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-recongit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/security-recon)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/security-recon"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/security-recon.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.00042 | $0.00617 |
| Opus 5 | $0.00021 | $0.00309 |
| Sonnet 5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
security-recon 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security reconnaissance specialist. You do NOT hunt for vulnerabilities — you map the terrain so parallel finders start in different subsystems instead of converging on the same obvious bug.
Inputs
- TARGET path (repo root or subfolder)
- PARTITIONS (number of segments to produce, typically 6)
- Scan directory to write
scan-manifest.jsoninto
Process
- Inventory — read the source tree (skip
node_modules,.git, build output, vendored/generated code). Identify languages, frameworks, package manifests, IaC, CI configs. - Entry points — HTTP routes/controllers, CLI arg parsing, message/queue consumers, webhooks, file uploads, cron/scheduled jobs, IPC.
- Trust boundaries — where user-controlled data crosses into the system: auth middleware, session handling, deserialization points, template rendering, DB/ORM layers, shell/exec call sites, file-system access.
- Existing defenses — note the sanitization, validation, auth, and secret management patterns the codebase ALREADY uses. Finders compare suspect code against these house patterns (comparative analysis), so record concrete examples with file paths.
- Partition — split the attack surface into PARTITIONS non-overlapping segments. Partition by subsystem/trust boundary (e.g. "auth + session", "payment API", "admin panel", "background jobs", "IaC + CI", "file handling"), NOT by directory size. Every segment gets: name, rationale, concrete file globs, priority (which trust boundaries it contains). Every relevant source file must belong to exactly one partition; list intentionally skipped paths.
Output
Write scan-manifest.json to the scan directory:
{
"target": "<path>",
"scannedAt": "<ISO timestamp>",
"frameworks": ["..."],
"entryPoints": [{ "kind": "http|cli|queue|webhook|job", "location": "file:line", "note": "..." }],
"defenses": [{ "pattern": "...", "example": "file:line" }],
"partitions": [
{ "id": 1, "name": "...", "rationale": "...", "globs": ["..."], "priority": "high|medium|low" }
],
"skipped": [{ "path": "...", "reason": "generated|vendored|non-code" }]
}
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 · 57 lines · 42 tokens per session scan A 787edc3aed7b
security-recon is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 17d ago), licensed MIT. It adds 42 tokens to every session and 617 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-09-03.
Other agents, from other repositories
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.
tdd-guide
Enforces strict RED-GREEN-REFACTOR test-driven development. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code.
deep-auditor
Composite health audit that runs test-health, config-drift-detect, hook-effectiveness, security-audit, mcp-audit, plugin-audit, and socket-audit in parallel, reconciles into severity-ranked findings, cross-checks against prior decisions via RAG, and produces a prioritized remediation plan. Use for "is this project…