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/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/security-auditor)<a href="https://agentmods.dev/agents/nota-america/forgecat-agent-profiles/security-auditor"><img src="https://agentmods.dev/badge/agents/nota-america/forgecat-agent-profiles/security-auditor.svg" alt="Measured on agentmods" 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.01065 |
| Opus 5 | $0.00017 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
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 8d 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- security-auditor — 86% identical, 29 lines differ
- security-auditor — 86% identical, 54 lines differ
- security-auditor — 86% identical, 29 lines differ
- security-auditor — 86% identical, 29 lines differ
- security-auditor — 83% identical, 35 lines differ
- security-auditor — 83% identical, 34 lines differ
- security-auditor — 80% identical, 65 lines differ
How it starts
The opening of the file, as written. The whole thing — 123 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?
Severity Classification
| Severity | Criteria | Action |
|---|---|---|
| Critical | Exploitable remotely, leads to data breach or full compromise | Fix immediately, block release |
| High | Exploitable with some conditions, significant data exposure | Fix before release |
| Medium | Limited impact or requires authenticated access to exploit | Fix in current sprint |
| Low | Theoretical risk or defense-in-depth improvement | Schedule for next sprint |
| Info | Best practice recommendation, no current risk | Consider adopting |
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.
- 8d ago First seen · 123 lines · 35 tokens per session scan A 1d06ecaa7a0a
security-auditor is an agent published in the GitHub repository nota-america/forgecat-agent-profiles (65 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 1,065 once invoked, about $0.0002 per session on Opus 5. 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.
shotgun-surgery-detector
Detecta duplicação sintática (jscpd) + semântica (embeddings OpenAI/pgvector) e gera SHOTGUN-SURGERY.md com clusters priorizados. Use ao suspeitar de shotgun surgery (cap 21 Feathers). (pesado).
assayer
You verify that built code actually delivers what the spec promised. Your power is order: you read the spec and form hard expectations before you look at the code, so you judge the code against the requirement — not the requirement against the code. The default assumption is that the code is broken; VERIFIED is…
wizard
Deep review, hard debugging, and "which approach" calls. Read-only. Use ONLY when the user explicitly asks for the wizard, when a party member calls it mid-encounter, or after two failed attempts at the same problem — not as a routine second opinion on ordinary work.
governance-specialist
Enforces engineering standards and code quality policies. Use when performing code reviews, standards audits, pre-commit checks, or compliance verification.