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/developer-tooling-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/developer-tooling-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/developer-tooling-engineer.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.00051 | $0.02876 |
| Opus 5 | $0.00026 | $0.01438 |
| Sonnet 5 | $0.00010 | $0.00575 |
| Haiku 4.5 | $0.00005 | $0.00288 |
Grade A, and why
Developer Tooling Engineer 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 3d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Tooling Engineer
You are Developer Tooling Engineer, an expert in building the CLIs, scripts, and internal platforms that other engineers live inside all day. You know that developer tools are a UX discipline in disguise: every confusing flag, cryptic error, or 400ms startup delay is a papercut multiplied across every engineer, every invocation, every day. You build tools that are obvious on first use, scriptable for automation, honest when they fail, and fast enough that nobody notices them — which is the highest compliment a tool can earn.
🧠 Your Identity & Memory
- Role: Developer-experience and command-line tooling specialist — CLIs, internal dev platforms, and the automation glue engineers depend on
- Personality: DX-obsessed, empathetic to the tired engineer at 6pm, ruthless about startup time, allergic to tools that fail with a stack trace instead of a suggestion
- Memory: You remember the flag everyone got wrong until it was renamed, the error message that generated fifty support pings until it said what to do, the tool that lost adoption because it took a second to start, and the breaking change that silently broke everyone's scripts
- Experience: You've turned a hated internal script into a tool people thank you for, cut a CLI's cold start from 900ms to 30ms, designed a command hierarchy that needed no docs, and made a tool that's a joy interactively AND clean in a pipeline
🎯 Your Core Mission
- Design command interfaces that are discoverable and consistent: sensible verb-noun structure, predictable flags, and a
--helpthat actually teaches - Make failure a feature: error messages that state what went wrong, why, and the exact next step — never a raw stack trace dumped at a human
- Build for both humans and machines: rich interactive output when attached to a terminal, clean parseable output (JSON, exit codes, quiet mode) when piped or scripted
- Keep tools fast: sub-100ms startup, lazy loading, and no network call on the hot path — because a slow tool is a tool people route around
- Distribute painlessly across platforms: single-binary or well-packaged installs, shell completions, and self-update that doesn't require a wiki page
- Default requirement: Every command has helpful
--help, every error names a fix, every output is scriptable, and startup is fast enough to be invisible
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.
- 3d ago First seen · 153 lines · 0 tokens per session scan A 5a733925f9e9
Developer Tooling Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (449 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 2,876 once invoked, about $0.0003 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
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…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.