Borrowing it
Nothing to install: this file belongs to davidmatousek/tachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/skills/tachi-threat-reporting/SKILL.mdgit clone --depth 1 https://github.com/davidmatousek/tachiWrote 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/skills/davidmatousek/tachi/tachi-threat-reporting)<a href="https://agentmods.dev/skills/davidmatousek/tachi/tachi-threat-reporting"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/tachi-threat-reporting/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/skills/davidmatousek/tachi/tachi-threat-reporting"><img src="https://agentmods.dev/badge/skills/davidmatousek/tachi/tachi-threat-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00493 |
| Opus 5 | $0.00026 | $0.00246 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
tachi-threat-reporting 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 8d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tachi-threat-reporting
Narrative threat report domain knowledge extracted from the tachi threat-report agent. This skill provides the templates, construction rules, and reference examples that the threat-report agent uses to transform structured threat model output into comprehensive narrative reports with Mermaid attack trees.
Domain Overview
The threat report agent produces two output types:
- threat-report.md -- A 7-section narrative report conforming to
schemas/report.yamlcontaining executive summary, architecture overview, per-category threat analysis, cross-cutting themes, Mermaid attack trees, remediation roadmap, and finding reference appendix - attack-trees/{finding-id}-attack-tree.md -- Standalone Mermaid attack tree files for every Critical and High finding
Report generation applies three bodies of domain knowledge:
- Narrative Templates -- Structural patterns for each report section: executive summary elements, architecture overview layout, per-category subsection headers, per-finding narrative pattern, progressive depth rules, cross-cutting theme detection criteria, and language conventions
- Attack Tree Construction -- Rules for building Mermaid flowchart attack trees: tree structure (root/intermediate/leaf), minimum depth requirements, decomposition stopping rules, Mermaid syntax conventions, color styling, node naming, and validation checklist
- Attack Tree Examples -- Reference implementations demonstrating correct syntax, naming, gate logic, and decomposition depth for Critical and High severity patterns
Loading Table
Reference files are loaded on-demand by the threat-report agent at specific workflow phases using the Read tool.
| Reference | File | Load When |
|---|---|---|
| Narrative Templates | references/narrative-templates.md |
Generating Executive Summary (Section 1), Architecture Overview (Section 2), Threat Analysis (Section 3), Cross-Cutting Themes (Section 4), Remediation Roadmap (Section 6) |
| Attack Tree Construction | references/attack-tree-construction.md |
Constructing Mermaid attack trees for Critical and High findings (Section 5) |
| Attack Tree Examples | references/attack-tree-examples.md |
Before generating the first attack tree -- load once as reference patterns |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 32 lines · 52 tokens per session scan A 0868afd6f5b8
tachi-threat-reporting is a skill published in the GitHub repository davidmatousek/tachi (92 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 493 once invoked, about $0.0003 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-03.
Other skills, from other repositories
usap-program-manager
Security program manager and passive lifecycle orchestrator (cs-security-program-manager). Use for security roadmap planning, program health scanning, debt tracking, facilitated reviews, or when the user says "security roadmap", "program planning", "security debt", "proactive scan", or "program review".
usap-red-teamer
Offensive security coordinator (cs-red-teamer). Use for red team campaign planning, attack path analysis, engagement scoping, adversary simulation, or when the user says "red team", "pentest", "attack simulation", "run an engagement", or "offensive security". Requires explicit authorization scope.
usap-alex
Universal USAP security advisor (cs-security-analyst). Use for any security question, alert triage (AT), threat hunt (TH), compromise assessment (CA), or when the user says "activate Alex", "start USAP", or asks what USAP can do.
usap-ciso
CISO and executive security advisor (cs-ciso-advisor). Use for board reports, executive risk briefings, regulatory gap assessments, cyber insurance inputs, or when the user says "board report", "CISO brief", "executive summary", "risk posture for leadership", or "regulatory update".
usap-incident-responder
Active incident command and response (cs-incident-responder). Use when there is a confirmed or suspected active incident, for containment decisions, forensic investigation, SEV declaration, or when the user says "declare incident", "start IR", "we have an active breach", or "forensics".
Obsidian
Create, edit, search, and manage Obsidian vault files using the Obsidian CLI and direct file operations. USE WHEN working with .md files in Obsidian vault, creating .base database views, creating .canvas visual canvases, searching notes, managing properties/tags, querying backlinks, OR user mentions wikilinks…