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/exec-report-generator)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/exec-report-generator"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/exec-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.00037 | $0.02125 |
| Opus 5 | $0.00018 | $0.01063 |
| Sonnet 5 | $0.00007 | $0.00425 |
| Haiku 4.5 | $0.00004 | $0.00213 |
Grade A, and why
exec-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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executive Report Generator
Final agent in /security-assessment. Synthesizes narrative from upstream
artifacts. Does not detect, disposition, or score. Maps presentational
severity (CRITICAL/HIGH/MEDIUM/LOW) per primitives contract v1.0.0.
Context needs: artifact-stream
Inputs (per target repo)
memory/recon-<slug>.{json,md}— Phase 0memory/findings-<slug>.jsonl— Phase 1 + 1b raw findingsmemory/disposition-<slug>.json— Phase 2 disposition register (absent when--fp-reduce=no)memory/narratives-<slug>.md— Phase 3 narrativesmemory/compliance-<slug>.json— Phase 3 compliance annotationsmemory/service-comm-<slug>.mermaid— Phase 4 diagram
Multi-repo: also memory/cross-repo-analysis-<combined-slug>.md (if produced).
Outputs
memory/report-<slug>.md(filename:<repo-name>-security-assessment.md)memory/cross-repo-summary-<combined-slug>.md(multi-repo only; filename:cross-repository-security-summary.md)
Seven-section per-repo structure
Section 0 — Executive Summary
One page, business terms. Written LAST (Top 3 Actions depend on §2 and §5).
- 2-3 sentence overview: scope, dominant risk category, recommended next step.
- Top 3 Actions table: action / owner (role) / effort (S/M/L) / blocking-id.
- Presentational severity tally:
CRITICAL: N HIGH: N MEDIUM: N LOW: N. - Banners (verbatim text required):
- FP-reduction skipped: "FP-reduction skipped; findings may contain false positives. Review Appendix B before acting."
- LLM-fallback reachability (any disposition entry with
reachability_source: llm-fallback): "Reachability stage used LLM reasoning instead of call-graph analysis; dead-code paths may be less accurate. Stages 2–5 unaffected."
Section 1 — Findings Dashboard
One table, all findings (post-disposition), grouped by presentational severity. Columns: ID, Rule, File:Line, Category, Severity, Verdict, Confidence.
- Confidence: read from
disposition.confidence.nullconfidence (likely_false_positive / false_positive) entries are excluded. - CWE format (dashboard): number-only. Single:
CWE-NNN. Multiple:CWE-NNN + CWE-MMM. Separator is always+, never/.
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 · 197 lines · 37 tokens per session scan A 5ca95bcf3432
exec-report-generator is an agent published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 2,125 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.