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 rules/ag-dmitry/composer-enhanced/05-red-teamgit clone --depth 1 https://github.com/AG-Dmitry/composer-enhancedWrote 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/ag-dmitry/composer-enhanced/05-red-team)<a href="https://agentmods.dev/rules/ag-dmitry/composer-enhanced/05-red-team"><img src="https://agentmods.dev/badge/rules/ag-dmitry/composer-enhanced/05-red-team.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 | $0.00026 | $0.00566 |
| Opus 5 | $0.00013 | $0.00283 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
05-red-team 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 5 — Red-team (Self-critique)
Persona: Critic. This is the phase that most distinguishes a thinking model from a guessing one. Switch hats completely: your job is to prove the Implementer wrong, not to confirm it. Assume there is at least one bug and go find it.
Mindset
- "Looks fine" is not an allowed conclusion. You must produce a concrete list of suspected failure points, then confirm or refute each one by reading the code.
- If you cannot find anything wrong, you have not looked hard enough — re-read the diff against the success criteria and edge cases one more time.
Attack checklist
Work through templates/red-team-checklist.md.
At minimum, hunt for:
- Requirement drift — does the code actually satisfy each phase-1 success criterion? Re-read them literally.
- Logic errors — off-by-one, inverted conditions, wrong operator, wrong variable.
- Null / undefined / empty — every input that could be missing.
- Async & lifecycle — unawaited promises, races, missing cleanup (subscriptions, timers, listeners), error rejection paths.
- Error handling — what happens on failure? Is it swallowed? Mislabeled?
- Regressions — what existing behavior or test could this break? Check call sites found in phase 2.
- Boundaries & contracts — types, validation at external boundaries, return shapes other code depends on.
- Hidden incompleteness — stubs, TODOs, hardcoded values presented as done.
- Project-specific gates — see
project-adapter.mdcfor your project's security, convention, and framework-specific checks.
Output
Record in the Red-team findings section of the task-memory file:
- Each suspected issue, with file/line.
- Verdict: confirmed bug / false alarm.
- For confirmed bugs: the fix, or a deliberate, justified acceptance.
A confirmed bug sends you to 07-reflect-retry.mdc to
fix it (this counts as part of the work, not a retry iteration unless the gates
in phase 6 had already run).
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.
- 5d ago First seen · 59 lines · 26 tokens per session scan A 93178ab93aaf
05-red-team is a cursor rule published in the GitHub repository AG-Dmitry/composer-enhanced (3 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 566 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.