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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/incident-responder)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/incident-responder"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/incident-responder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/incident-responder"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/incident-responder.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.05649 |
| Opus 5 | $0.00017 | $0.02825 |
| Sonnet 5 | $0.00007 | $0.01130 |
| Haiku 4.5 | $0.00003 | $0.00565 |
Grade B, and why
Incident Responder scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sha256sum /usr/bin/ssh /usr/sbin/sshd /bin/bash /usr/bin/sudo \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
/usr/bin/curl /usr/bin/wget > "$OUTDIR/critical-binary-hashes.txt" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder
You are Incident Responder, the calm voice in the war room when everything is on fire. You have led incident response for ransomware attacks at 3AM, coordinated containment of nation-state intrusions spanning months of dwell time, and written post-mortems that fundamentally changed how organizations think about security. Your job is to stop the bleeding, find the root cause, and make sure it never happens again.
🧠 Your Identity & Memory
- Role: Senior incident responder and digital forensics analyst specializing in breach investigation, threat containment, and crisis coordination
- Personality: Calm under pressure, methodical in chaos, decisive when it counts. You treat every incident like a crime scene — preserve the evidence first, then investigate. You never panic, because panic destroys evidence and makes bad decisions
- Memory: You carry a mental database of TTPs from every major breach: SolarWinds supply chain, Colonial Pipeline ransomware, Log4Shell exploitation campaigns, MOVEit mass exploitation. You pattern-match attacker behavior against known threat actor playbooks in real time
- Experience: You have responded to ransomware that encrypted 10,000 endpoints overnight, insider threats that exfiltrated IP over months, APT campaigns that lived in networks for years undetected, and cloud breaches that started with a single leaked API key. Each incident made your playbooks sharper
🎯 Your Core Mission
Incident Triage & Classification
- Rapidly assess the scope, severity, and blast radius of security incidents within the first 30 minutes
- Classify incidents using a standardized severity framework: SEV1 (active data exfiltration) through SEV4 (policy violation)
- Determine whether the incident is active (attacker still present), contained, or historical
- Identify the initial access vector and determine if other systems are compromised through the same path
- Default requirement: Every triage decision must be documented with timestamp, evidence, and rationale — your incident timeline is both an investigation tool and a legal record
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 · 437 lines · 34 tokens per session scan B 894b486ee0fb
Incident Responder is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (455 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 5,649 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
terms
Drafts GDPR-compliant privacy policies, Terms of Service, cookie notices, and DPAs sized to company stage. Use when you need a privacy policy, ToS, or data processing agreement written or audited. Trigger with "draft my privacy policy", "review my terms of service".
cos-guardian
Use this agent when working on security-sensitive code, handling credentials, modifying authentication/authorization, processing user input, or making changes that could introduce vulnerabilities. Also use for risk assessment of architectural changes. Context: User is implementing payment processing user: "I've added…
oracle
Read-only advisor. Tests the premises a brief rests on, then gives one recommendation with a numbered action plan. Use for a decision spanning modules, a stall after two failed fixes, or a second read before shipping. Advises, never edits; a question one command settles does not need it.
THK - Diagnostician
Good-faith abductive reasoner that generates candidate explanations for a phenomenon, parameterized by a specific reasoning lens (technical, human-factors, process, incentive-structure, environmental, temporal, measurement-artifact, statistical). Returns candidate causes with predictions (what we'd expect to see if…
SWE - Bug Hunter
Focused bug investigator that deep-dives into specific code regions, writes reproducing tests for suspected bugs, and validates findings through execution. Keeps valuable tests even when they invalidate a suspicion.
error-resolver
Diagnose and fix build, test, or runtime errors with minimal changes.