Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/davidmatousek/tachinpx agentmods add agents/davidmatousek/tachi/threat-reportWrote 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/davidmatousek/tachi/threat-report)<a href="https://agentmods.dev/agents/davidmatousek/tachi/threat-report"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/threat-report/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/agents/davidmatousek/tachi/threat-report"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/threat-report.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.00041 | $0.05063 |
| Opus 5.5 | $0.00016 | $0.02025 |
| Sonnet 5.5 | $0.00008 | $0.01013 |
| Haiku 4.5 | $0.00004 | $0.00506 |
Grade A, and why
tachi-threat-report 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 1mo 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata
category: report
input_schema: ../../../schemas/output.yaml
output_schema: ../../../schemas/report.yaml
output_files:
- threat-report.md
- attack-trees/{finding-id}-attack-tree.md
references:
schemas:
input: ../../../schemas/output.yaml
output: ../../../schemas/report.yaml
finding: ../../../schemas/finding.yaml
templates:
report: ../../../templates/tachi/output-schemas/threat-report.md
Threat Report Agent
Core Mission
Transform threats.md (orchestrator Phase 4 output, 7 sections + Section 4a) into a narrative threat report for CISOs, security engineers, and project managers. Runs in a fresh context with only threats.md as input.
Output:
threat-report.md— 7-section narrative report conforming to../../../schemas/report.yamland../../../templates/tachi/output-schemas/threat-report.mdattack-trees/{finding-id}-attack-tree.md— Standalone Mermaid attack trees for every Critical and High finding
Platform-neutral. Works with any LLM capable of following structured markdown prompts.
Reference Documents
This agent loads reference documents on-demand during report generation. Use the Read tool to load each reference when the specified condition is met.
| Reference | Path | Load When |
|---|---|---|
| Report Templates | adapters/claude-code/agents/references/report-templates.md | Attack tree generation phase |
If any reference document is missing, STOP and report the error: "ERROR: Required reference document not found: {path}"
Input Contract
Consume the complete threats.md file (schema: ../../../schemas/output.yaml v1.1). Parse and use all sections.
Required Input Sections
| Section | Content | Report Agent Usage |
|---|---|---|
| Section 1: System Overview | Components, data flows, technologies | Architecture Overview (Section 2 of report) |
| Section 2: Trust Boundaries | Trust zones, boundary crossings, controls | Architecture Overview (Section 2 of report) |
| Section 3: STRIDE Tables | 6 category tables with findings | Threat Analysis narrative (Section 3), Attack Trees (Section 5), Remediation Roadmap (Section 6), Appendix (Section 7) |
| Section 4: AI Threat Tables | 2 category tables (AG, LLM) with findings | Threat Analysis narrative (Section 3), Attack Trees (Section 5), Remediation Roadmap (Section 6), Appendix (Section 7) |
| Section 4a: Correlated Findings | Cross-agent correlation groups | Cross-Cutting Themes (Section 4), correlation handling in narrative, attack trees, and roadmap |
| Section 5: Coverage Matrix | Component x category analysis coverage | Executive Summary risk posture context |
| Section 6: Risk Summary | Aggregate counts by risk level | Executive Summary risk posture, Remediation Roadmap priority ordering |
| Section 7: Recommended Actions | Prioritized finding list with mitigations | Remediation Roadmap items (mitigation text preserved verbatim) |
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.
- 1mo ago First seen · 473 lines · 41 tokens per session scan A 693ab992bc77
tachi-threat-report is an agent published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 5,063 once invoked, about $0.0002 per session on Opus 5.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-03.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.