Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/adriannoes/awesome-agentic-aiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/adriannoes/awesome-agentic-ai/security-audit)<a href="https://agentmods.dev/commands/adriannoes/awesome-agentic-ai/security-audit"><img src="https://agentmods.dev/badge/commands/adriannoes/awesome-agentic-ai/security-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/adriannoes/awesome-agentic-ai/security-audit"><img src="https://agentmods.dev/badge/commands/adriannoes/awesome-agentic-ai/security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00178 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
security-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Security Audit
Source: hamzafer/cursor-commands (MIT)
Overview
Comprehensive security review to identify and fix vulnerabilities in the codebase.
Steps
-
Dependency audit
- Check for known vulnerabilities
- Update outdated packages
- Review third-party dependencies
-
Code security review
- Check for common vulnerabilities (injection, XSS, etc.)
- Review authentication/authorization
- Audit data handling practices
-
Infrastructure security
- Review environment variables
- Check access controls
- Audit network security
Security Checklist
- Dependencies updated and secure
- No hardcoded secrets
- Input validation implemented
- Authentication secure
- Authorization properly configured
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 33 lines · 0 tokens per session scan A 50b3829dcc62
security-audit is a command published in the GitHub repository adriannoes/awesome-agentic-ai (57 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
assistant-auto
Orchestrator in automatic mode. Choose the workflow that semantically fits based on the request + the injected repo context, then execute immediately via Skill.
growth-email
Create transactional and marketing email templates.
amby.clarify
Resolve the open [NEEDS CLARIFICATION] markers in a feature spec.
aw-upgrade
Upgrade gh-aw extension, recompile and validate all workflows, and open a PR with changes.
review
Conduct a five-axis code review — correctness, readability, architecture, security, performance.