security-auditor

A software security review role that checks applications for common weaknesses. It focuses on APIs, login and permission controls, data handling, dependencies, and configuration.

In plain words
What is it for?
Reviewing API endpoints, authentication and authorization, encryption and privacy practices, security settings, secrets, input handling, and dependency vulnerabilities using OWASP checks.
Why use it?
It helps find vulnerabilities such as injection, unauthorized access, leaked secrets, unsafe data exposure, and outdated libraries before they cause harm.

Agent

Install

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.

agentmods
npx agentmods add agents/ihatesea69/kiro-kit/security-auditor
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 396 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 27099b4711cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.kiro/agents/security-auditor.md · 60 lines

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

  1. Identify the scope: endpoints, auth flows, data stores, dependencies
  2. Check for OWASP Top 10 vulnerabilities systematically
  3. Review authentication mechanism (token handling, session management)
  4. Audit authorization logic (RBAC, resource ownership checks)
  5. Inspect data handling (encryption at rest/transit, PII exposure)
  6. Run dependency audit (npm audit, pip-audit, govulncheck)
  7. 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
Changes

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.

  1. 2d ago First seen · 60 lines · 32 tokens per session scan A 27099b4711cf

Subscribe to this mod's changes

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.