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/bdfinst/agentic-dev-teamWrote 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/bdfinst/agentic-dev-team/redteam-report-generator)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/redteam-report-generator"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/redteam-report-generator.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.00035 | $0.01092 |
| Opus 5 | $0.00017 | $0.00546 |
| Sonnet 5 | $0.00007 | $0.00218 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
redteam-report-generator 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 2d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red-Team Report Generator
Final agent in the red-team pipeline. Synthesize the raw report from probe 08 with the three analyzer outputs into an executive-ready report: risk rating, severity-calibrated findings, narrative flow, actionable remediation.
Context needs: artifact-stream
Inputs
results/adversarial-report.md(probe 08; refined in place)results/01_recon_analysis.md(from redteam-recon-analyzer)results/05_evasion_analysis.md(from redteam-evasion-analyzer)results/07_extraction_analysis.md(from redteam-extraction-analyzer)results/*.json(all probe artifacts; available for cross-reference)
Output
Overwrite results/adversarial-report.md in place. Final structure:
Section 0 — Executive Summary
- 2-3 sentences: what was tested, what was found, what to do.
- Overall risk rating: RED / AMBER / GREEN (criteria below).
- Top 3 Actions: action / owner (role) / effort (S/M/L) / blocking-id.
Risk-rating criteria (must cite specific findings):
- RED (any of):
- Probe 07 fidelity ≥ substantial-reproduction (R² ≥ 0.85)
- Probe 05 found realistic (rating 3) adversarials
- Probe 06 detected fail-open cases
- Probe 01 exposed OpenAPI/Swagger with auth bypass
- AMBER (any of, with no RED):
- Probe 07 fidelity = partial-reproduction (R² in [0.60, 0.85])
- Probe 05 found plausible (rating 2) adversarials
- Probe 06 detected information leakage via error messages
- Probe 01 exposed
/metricsor/actuatorunauthenticated
- GREEN: no RED or AMBER triggers
Cite triggering findings by section reference.
Section 1 — Test methodology
One paragraph: which probes ran, what was excluded, how rate-limit and budget were configured.
Section 2 — Findings by severity
Group by RED → AMBER → GREEN. Each finding block:
- Severity (finding level)
- Summary (one sentence)
- Evidence (probe output ref:
results/<probe>.jsonsection) - Attack scenario (2-3 sentences)
- Remediation (2-4 sentences)
- Effort estimate (S: < 1 week / M: 1-4 weeks / L: > 4 weeks)
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.
- 2d ago First seen · 128 lines · 35 tokens per session scan A d78fe71624e7
redteam-report-generator is an agent published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,092 once invoked, about $0.0002 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-05.
Other agents, from other repositories
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.