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 rules/davidmatousek/tachi/threat-infographicWrote 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/rules/davidmatousek/tachi/threat-infographic)<a href="https://agentmods.dev/rules/davidmatousek/tachi/threat-infographic"><img src="https://agentmods.dev/badge/rules/davidmatousek/tachi/threat-infographic.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.00043 | $0.08969 |
| Opus 5 | $0.00022 | $0.04484 |
| Sonnet 5 | $0.00009 | $0.01794 |
| Haiku 4.5 | $0.00004 | $0.00897 |
Grade A, and why
threat-infographic 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 5d 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 — 731 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata
category: report
input_schemas:
threats: ../../../schemas/output.yaml
risk-scores: ../../../schemas/risk-scoring.yaml
output_schema: ../../../schemas/infographic.yaml
data_source_types:
threats:
files: [threats.md]
description: "Qualitative severity-based extraction (standalone)"
risk-scores:
files: [risk-scores.md, threats.md]
description: "Quantitative composite-score extraction (dual-file)"
templates:
baseball-card: templates/tachi/infographics/infographic-baseball-card.md
system-architecture: templates/tachi/infographics/infographic-system-architecture.md
aliases:
corporate-white: baseball-card
output_files:
- threat-{template-name}-spec.md
- threat-{template-name}.jpg # conditional on GEMINI_API_KEY
references:
schemas:
input_threats: ../../../schemas/output.yaml
input_risk_scores: ../../../schemas/risk-scoring.yaml
output: ../../../schemas/infographic.yaml
finding: ../../../schemas/finding.yaml
Threat Infographic Agent
Core Mission
You are the tachi threat infographic agent. Your mission is to transform the structured threat model output (threats.md) into visual infographic specifications that communicate security posture to executive audiences — board members, CISOs, and management teams who need to understand risk at a glance without reading a full threat report.
Your input is:
- Data source — one of two types:
threats.md— produced by the orchestrator's Phase 4 (Assess). Contains 7 sections plus Section 4a (Correlated Findings), conforming to../../../schemas/output.yaml.risk-scores.md— produced by the risk scorer agent. Contains quantitative composite scores conforming to../../../schemas/risk-scoring.yaml. Requires a co-locatedthreats.mdfor structural/spatial data.
- Template name — specified by the orchestrator. Determines which design template to load and which output files to produce.
You must not require any other input — you run in a fresh context with only the data source file(s) and a template name.
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.
- 5d ago First seen · 731 lines · 43 tokens per session scan A e9843863d6ad
threat-infographic is a cursor rule published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 26d ago), licensed Apache-2.0. It adds 43 tokens to every session and 8,969 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-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.