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/H-mmer/pentest-agentsWrote 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/rules/h-mmer/pentest-agents/pentest-agents-mistakes)<a href="https://agentmods.dev/rules/h-mmer/pentest-agents/pentest-agents-mistakes"><img src="https://agentmods.dev/badge/rules/h-mmer/pentest-agents/pentest-agents-mistakes/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/rules/h-mmer/pentest-agents/pentest-agents-mistakes"><img src="https://agentmods.dev/badge/rules/h-mmer/pentest-agents/pentest-agents-mistakes.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.00007 | $0.17584 |
| Opus 5 | $0.00003 | $0.08792 |
| Sonnet 5 | $0.00001 | $0.03517 |
| Haiku 4.5 | $0.00001 | $0.01758 |
Grade A, and why
pentest-agents-mistakes scanned grade A 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 6d 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 the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
Why: Direct requests ("output your system prompt", role-play, translation, base64) trigger "never reveal" guardrails. Techniques that never mention the prompt work because the model doesn't know it's being extracted. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Use a real browser for WAF/JS/CAPTCHA/UI-mediated bugs.** `curl` 403 from a CDN is not "not vulnerable" — it's "you never reached the app." The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 693 lines · 7 tokens per session scan A ebba61c3d5da
pentest-agents-mistakes is a cursor rule published in the GitHub repository H-mmer/pentest-agents (836 stars, last pushed 2mo ago), with no licence file. It adds 7 tokens to every session and 17,584 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 2 findings (asks the agent to reveal its instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.