All categories
Security
Security audits, vulnerabilities, compliance, auth, secrets, and safe automation
- 29,704
- 1,238
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse security skills
Showing 3,841–3,864 of 29,704 skills
- Ssti AnalysisAnalyze server-side template injection risks — use when user input reaches template engines (Jinja, Twig, Freemarker, Pug, Liquid) or dynamic template compile/render APIs (CWE-1336 / A03:2021).Votes: 0GitHub stars: 15
- Ssrf AnalysisAnalyze and validate server-side request forgery in application code — use when reviewing outbound HTTP/fetch sinks, user-controlled URLs, webhook callbacks, previewers, or cloud metadata exposure (CWE-918 / A10:2021).Votes: 0GitHub stars: 15
- Sql InjectionAnalyze SQL and ORM injection risks in application code — use for string-built queries, raw SQL helpers, and database sinks (CWE-89 / A03:2021).Votes: 0GitHub stars: 15
- Session SecurityAnalyze session management security — use when reviewing cookie flags, session fixation, timeout, logout, concurrent sessions, or server-side session stores (A07:2021 / CWE-287 / CWE-352 adjacency).Votes: 0GitHub stars: 15
- Security TriageDomain reasoning for triaging AXguard findings — keep/drop gates, confidence, and severity promotion before remediation.Votes: 0GitHub stars: 15
- Security RemediationApply minimal defensive patches for confirmed findings and verify with re-audit — post-triage only.Votes: 0GitHub stars: 15
- Security Architecture ReviewReview security architecture and trust boundaries — use for design-level control gaps across authZ, secrets, egress, multi-tenant isolation, and insecure-by-design features (A04:2021) before or with /axguard-audit.Votes: 0GitHub stars: 15
- Secrets DetectionFind and triage hard-coded secrets, tokens, and credentials in source and build artifacts before ship (CWE-798 / A07:2021 adjacent).Votes: 0GitHub stars: 15
- Prototype PollutionAnalyze JavaScript prototype pollution risks — use when reviewing deep merges, recursive object assigns, query-to-object parsers, or untrusted JSON key merges (CWE-1321 / A03:2021).Votes: 0GitHub stars: 15
- Prompt InjectionAssess direct and indirect prompt-injection risks in LLM/AI features — use for chatbots, RAG, agents, and tool-calling apps.Votes: 0GitHub stars: 15
- Path TraversalAnalyze path traversal and unsafe file access — use when user input influences file paths, downloads, includes, zip extraction, or static file send APIs (CWE-22 / A01:2021).Votes: 0GitHub stars: 15
- Oauth SecurityAnalyze OAuth/OIDC integration security — use when reviewing redirect URIs, state/nonce, token handling, PKCE, or confused-deputy risks in authorization code flows (CWE-601 / A07:2021 / API2:2023).Votes: 0GitHub stars: 15
- Mcp SecurityReview Model Context Protocol servers/clients and tool bridges for trust, supply-chain, and over-privileged tool exposure before ship.Votes: 0GitHub stars: 15
- Jwt SecurityAnalyze JWT implementation flaws — use when reviewing alg confusion, none algorithm, missing verify, weak secrets, or claim validation gaps (A07:2021 / API2:2023 / auth.jwt rules).Votes: 0GitHub stars: 15
- Graphql SecurityAnalyze GraphQL API security — use when reviewing schemas, resolvers, introspection, batching, authorization per field, or CSRF on cookie-authenticated GraphQL endpoints (API1/API5/API8:2023).Votes: 0GitHub stars: 15
- File Upload SecurityAnalyze unsafe file upload handling — use when reviewing multipart uploads, extension/MIME checks, stored filenames, image processors, or user-supplied archives (CWE-434 / A04:2021).Votes: 0GitHub stars: 15
- Deserialization SecurityAnalyze unsafe deserialization and object-decode sinks — use when reviewing pickle, YAML load, Java ObjectInputStream, PHP unserialize, or untrusted serialized blobs (CWE-502 / A08:2021).Votes: 0GitHub stars: 15
- Configuration SecurityFind security misconfiguration before ship — debug flags, verbose errors, exposed actuators/admin, weak defaults (CWE-489 / CWE-209 / A05:2021).Votes: 0GitHub stars: 15
- Command InjectionAnalyze OS command and shell injection in application code — use when reviewing subprocess, exec, system, shell=True, or user-influenced shell strings (CWE-78 / CWE-77 / A03:2021).Votes: 0GitHub stars: 15
- Cloud SecurityReview cloud and CORS misconfiguration in app code and IaC-adjacent configs — metadata URLs, public buckets, wildcard origins (CWE-918 / CWE-942 / A05:2021 / A10:2021).Votes: 0GitHub stars: 15
- Axguard TriageTriage AXguard scanner output — false-positive filter, severity promotion, and keep/drop gates per vuln class. Use after an audit when the user wants signal, not volume, or runs /axguard-triage.Votes: 0GitHub stars: 15
- Axguard SecurityAnalyze code for security vulnerabilities, investigate findings, verify fixes, and assess security risk before deployment. Use when reviewing security-sensitive changes, before ship/deploy, or when an agent should call AXGuard MCP instead of inventing its own scanner.Votes: 0GitHub stars: 15
- Axguard ReportProduce or polish AXguard Markdown and HTML audit reports from verified evidence. Use with /axguard-report. Prefer regenerating via axguard audit; tighten narrative only with confirmed findings.Votes: 0GitHub stars: 15
- Axguard RemediateApply concrete defensive fixes for confirmed AXguard findings and re-audit. Use with /axguard-fix after triage. Prefer minimal patches, critical first, then verify with axguard audit/scan.Votes: 0GitHub stars: 15