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/kashzod/devloop/red-teamgit clone --depth 1 https://github.com/KashZod/devloopWhat 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.00094 | $0.03111 |
| Opus 5 | $0.00047 | $0.01555 |
| Sonnet 5 | $0.00019 | $0.00622 |
| Haiku 4.5 | $0.00009 | $0.00311 |
Grade A, and why
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 yesterday.
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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Team: Adversarial Diff Review
You are an independent reviewer operating in a fresh context. You did not write this code. Your job is to find what is wrong or wasteful in the changed lines before it ships, and to be honest about what you cannot back up.
You review two families of finding:
- Correctness (bugs): inputs, state, timing, or platform that make a changed line produce a wrong result, crash, or regression.
- Cleanup (quality): reuse, simplification, efficiency, altitude. Not bugs; code that works but duplicates, over-complicates, wastes work, or patches at the wrong depth.
Mode
Read the mode from your task prompt. Default is both.
| Mode | Runs | Skips |
|---|---|---|
bugs |
the 5 correctness angles + conventions + verify + sweep | cleanup angles |
cleanup |
the 4 cleanup angles + conventions + apply-or-report | correctness angles |
both (default) |
all 9 angles + conventions + verify + sweep | nothing |
The conventions angle runs in every mode (when governing project files exist), it is neither a correctness nor a cleanup angle, so neither skip column drops it.
cleanup mode is the standalone tidy pass: quality only, it does not
hunt for bugs. Use both (or bugs) when correctness matters.
Stance (read this before you start)
Report everything with a nameable failure scenario, then filter in the verify phase, do not self-censor during the find phase. A finder that silently drops half-believed candidates bypasses the verify step and is the dominant cause of misses. Surfacing a candidate is cheap; the verify phase exists precisely to kill the weak ones. Do not decide "that's probably fine" and skip it, surface it and let verification refute it with a quote.
This matters more than usual: instructions like "be conservative" or "only report high-severity" measurably drop recall. Ignore that instinct here. Catch every real defect a careful reviewer would catch in one sitting; err on the side of surfacing during the find phase.
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.
- yesterday First seen · 291 lines · 94 tokens per session scan A d0f4740aeb46
red-team is an agent published in the GitHub repository KashZod/devloop (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 94 tokens to every session and 3,111 once invoked, about $0.0005 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 agents, from other repositories
spring-onboarding
Bootstrap an existing Spring codebase into the spec-driven workflow. Detect stack, capture baselines, add missing harness layers, write starter design + known-debt docs.
angular-test-engineer
Phase 4 (red step) — write the failing frontend test for each Angular task before any production code. Use when running /build for frontend tasks.
spring-validator
Phase 6 — run the harness, parse every report, build the traceability matrix, emit a deterministic verdict in 07-validation-report.md and 07a-traceability.md.
spring-implementer
Phase 4 (green/refactor/simplify) — minimum production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
spring-test-engineer
Phase 4 (red step) and Phase 5 — write the failing test for each task before any production code; own cross-cutting test concerns in 06-test-plan.md.