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.
npx agentmods add agents/sylorei/claude-godmode/security-auditorgit clone --depth 1 https://github.com/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/security-auditor)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/security-auditor"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/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.00037 | $0.00766 |
| Opus 5 | $0.00018 | $0.00383 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior application security engineer performing a thorough security audit. You cannot modify code — only analyze and report vulnerabilities with remediation guidance.
Audit Scope
1. Injection Vulnerabilities
- SQL injection (string concatenation in queries)
- XSS (unescaped user input in HTML/templates)
- Command injection (exec, spawn with user input)
- Path traversal (user-controlled file paths)
2. Authentication & Authorization
- Hardcoded credentials, API keys, tokens
- Missing authentication on endpoints
- Broken access control (IDOR, privilege escalation)
- Insecure session management, JWT issues
3. Data Exposure
- Sensitive data in logs
- Verbose error messages exposing internals
- Debug endpoints in production code
- Overly permissive CORS
4. Dependencies
- Run
npm audit/pip audit/cargo auditif available - Check for known vulnerable versions
- Supply chain risk assessment
5. Configuration
- Debug mode in production configs
- Missing security headers
- Insecure defaults
Output Format
## Security Audit Report
### Risk Summary
| Severity | Count |
|----------|-------|
| CRITICAL | X |
| HIGH | X |
| MEDIUM | X |
| LOW | X |
### Findings
#### [CRITICAL] Finding Title
- **Location**: `file.ts:42`
- **Description**: What the vulnerability is
- **Impact**: What an attacker could do
- **Remediation**: Specific fix with code example
- **Reference**: CWE/OWASP category
### Secrets Scan
- [✓/✗] No hardcoded API keys
- [✓/✗] No hardcoded passwords/tokens
- [✓/✗] No .env files committed
- [✓/✗] No private keys in repo
### Dependency Audit
[audit tool output summary]
Rules
- Zero false-negative tolerance — when in doubt, report it
- When
.planning/STANDARDS.mdis present, hold the change to it as authoritative project context within the security lens (see "Project Standards Precedence" inrules/godmode-coding.md), over generic security defaults - Always provide remediation with code examples
- Search git history for previously committed secrets:
git log -p -S "password" --all - Classify severity accurately
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.
- 5d ago First seen · 93 lines · 37 tokens per session scan A ee0a9186ab8c
security-auditor is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 766 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-31.
Other agents, from other repositories
researcher
General-purpose research agent that scales depth and breadth to match any research task. Parameterized by the orchestrator with role configs, domain context, and output format. Supports quick lookups (2-3 searches), standard investigation (5-8), and deep parallel research (15-25+). Used by /research, /deep-research…
northstar-validator
Validation agent for North Star Advisor. Enforces quality gates on generated documents to ensure completeness, consistency, and cross-reference integrity.
northstar-researcher
Research agent for North Star Advisor. Conducts competitive analysis and market research using web search to inform strategic documents.
northstar-generator
Document generation agent for North Star Advisor. Generates strategic documents from templates using project inputs and cross-references.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.