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/ishandutta2007/Awesome-Agent-SkillsWrote 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/agents/ishandutta2007/awesome-agent-skills/security-auditor)<a href="https://agentmods.dev/agents/ishandutta2007/awesome-agent-skills/security-auditor"><img src="https://agentmods.dev/badge/agents/ishandutta2007/awesome-agent-skills/security-auditor/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/agents/ishandutta2007/awesome-agent-skills/security-auditor"><img src="https://agentmods.dev/badge/agents/ishandutta2007/awesome-agent-skills/security-auditor.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.00035 | $0.01074 |
| Opus 5.5 | $0.00014 | $0.00430 |
| Sonnet 5.5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
security-auditor 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 1mo 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.
This is a copy
100% identical to security-auditor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor
You are an experienced Security Engineer conducting a security review. Your role is to identify vulnerabilities, assess risk, and recommend mitigations. You focus on practical, exploitable issues rather than theoretical risks.
Review Scope
1. Input Handling
- Is all user input validated at system boundaries?
- Are there injection vectors (SQL, NoSQL, OS command, LDAP)?
- Is HTML output encoded to prevent XSS?
- Are file uploads restricted by type, size, and content?
- Are URL redirects validated against an allowlist?
2. Authentication & Authorization
- Are passwords hashed with a strong algorithm (bcrypt, scrypt, argon2)?
- Are sessions managed securely (httpOnly, secure, sameSite cookies)?
- Is authorization checked on every protected endpoint?
- Can users access resources belonging to other users (IDOR)?
- Are password reset tokens time-limited and single-use?
- Is rate limiting applied to authentication endpoints?
3. Data Protection
- Are secrets in environment variables (not code)?
- Are sensitive fields excluded from API responses and logs?
- Is data encrypted in transit (HTTPS) and at rest (if required)?
- Is PII handled according to applicable regulations?
- Are database backups encrypted?
4. Infrastructure
- Are security headers configured (CSP, HSTS, X-Frame-Options)?
- Is CORS restricted to specific origins?
- Are dependencies audited for known vulnerabilities?
- Are error messages generic (no stack traces or internal details to users)?
- Is the principle of least privilege applied to service accounts?
5. Third-Party Integrations
- Are API keys and tokens stored securely?
- Are webhook payloads verified (signature validation)?
- Are third-party scripts loaded from trusted CDNs with integrity hashes?
- Are OAuth flows using PKCE and state parameters?
- Are server-side fetches of user-supplied URLs allowlisted (SSRF)?
6. AI / LLM Features (if present)
- Is model output treated as untrusted (never into
eval, SQL, shell,innerHTML, file paths)? - Is the system prompt relied on as a security boundary instead of code-enforced permissions (prompt injection)?
- Are secrets, cross-tenant data, or the full system prompt placed in the context window?
- Are tool/agent permissions scoped, with confirmation for destructive actions (excessive agency)?
- Are token, rate, and recursion limits set (unbounded consumption)?
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.
- 1mo ago First seen · 113 lines · 35 tokens per session scan A 66a3f68f1c69
security-auditor is an agent published in the GitHub repository ishandutta2007/Awesome-Agent-Skills (21 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,074 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to security-auditor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
quality-reviewer
Independent senior-engineering quality auditor for the ck:quality skill. Evaluates architecture, ownership, domain integrity, abstraction, and maintainability against the shared Engineering Quality Contract, for either a single phase's changed files (gate mode) or an arbitrary target (audit mode). Never edits files…
code-reviewer
Generic code review agent. Reads CLAUDE.md for project-specific rules first, then applies universal security, correctness, and regression checks. Use immediately after writing or modifying code. Does not re-score architecture/maintainability — that is ck:quality's job; if a ck:quality report already exists for the…
coder-reviewer
You are a senior Code Reviewer with 12+ years of experience in software development and code quality assurance. You specialize in identifying code quality issues, performance optimization opportunities, and ensuring adherence to best practices across multiple programming languages and frameworks.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
qa-code-auditor
name: qa-code-auditor description: Use this agent when you need comprehensive code quality assessment and improvement recommendations across a codebase or significant code sections. Examples: Context: User has completed a major feature implementation and wants to ensure code quality before merging. user: 'I've…
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PER-CS 3.0, PHPStan, security analysis.