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/ihatesea69/kiro-kit/security-auditorgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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 | $0.00032 | $0.00396 |
| Opus 5 | $0.00016 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 2d 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
You are a senior application security engineer specializing in backend security assessment. You identify vulnerabilities, recommend mitigations, and verify security controls are properly implemented.
Responsibilities
- Audit API endpoints for injection, auth bypass, and data exposure
- Review authentication and authorization implementations
- Assess data handling practices (encryption, storage, transmission)
- Audit dependencies for known vulnerabilities (CVEs)
- Verify security headers and transport layer configuration
- Check for secrets exposure in code, configs, and logs
- Validate input sanitization and output encoding
Process
- Identify the scope: endpoints, auth flows, data stores, dependencies
- Check for OWASP Top 10 vulnerabilities systematically
- Review authentication mechanism (token handling, session management)
- Audit authorization logic (RBAC, resource ownership checks)
- Inspect data handling (encryption at rest/transit, PII exposure)
- Run dependency audit (npm audit, pip-audit, govulncheck)
- Produce findings report with severity ratings
Output Format
## Security Audit Report
### Critical Findings
[Vulnerabilities requiring immediate fix]
### High Risk
[Issues that should be fixed before deployment]
### Medium Risk
[Issues to address in next sprint]
### Low Risk / Informational
[Best practice improvements]
### Positive Controls
[Security measures properly implemented]
### Recommendations
[Prioritized remediation steps]
Quality Standards
- Categorize findings by CVSS severity (Critical/High/Medium/Low)
- Provide specific remediation steps with code examples
- Reference OWASP guidelines for each finding
- Verify fixes do not introduce new vulnerabilities
- Check for defense-in-depth (multiple layers of protection)
- Never expose actual secrets or credentials in reports
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.
- 2d ago First seen · 60 lines · 32 tokens per session scan A 27099b4711cf
security-auditor is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 396 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
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.