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/commands/tachi.security-report.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/commands/davidmatousek/tachi/tachi.security-report)<a href="https://agentmods.dev/commands/davidmatousek/tachi/tachi.security-report"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/tachi.security-report.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.00083 | $0.03140 |
| Opus 5 | $0.00042 | $0.01570 |
| Sonnet 5 | $0.00017 | $0.00628 |
| Haiku 4.5 | $0.00008 | $0.00314 |
Grade A, and why
tachi.security-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 7d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
Consider user input before proceeding (if not empty).
Step 0: Parse Arguments
-
If
$ARGUMENTScontains--output-dir <path>:- Set
output_dirto the specified path - Strip
--output-dir <path>from$ARGUMENTS(trim extra whitespace)
- Set
-
Default:
output_dir = null(resolved in Step 1 based on target directory) -
If
$ARGUMENTScontains--title <value>:- Set
title_overrideto the specified value (may be quoted:--title "Custom Project Name") - Strip
--title <value>from$ARGUMENTS(trim extra whitespace)
- Set
-
Default:
title_override = null(auto-detected fromthreats.mdfrontmatter in agent) -
Remaining
$ARGUMENTSis treated as the target directory path. -
If no target directory was provided in
$ARGUMENTS:- If
./docs/security/exists in cwd: globdocs/security/*/, sort directory names descending (ISO-likeYYYY-MM-DDTHH-MM-SStimestamps sort correctly as strings), and select the newest directory that containsthreats.md(the minimum required artifact). Settarget_dirto that path and display:Auto-detected target: {target_dir}. - Otherwise, default to current working directory (
.).
- If
Overview
Single-command entry point for tachi security assessment PDF generation — the final stage in the pipeline: /threat-model -> /risk-score -> /compensating-controls -> /infographic -> /security-report. Auto-detects all available tachi artifacts in the target directory, determines which pages to include based on artifact availability, and produces a professional multi-page PDF booklet via Typst.
Flow: Parse -> Validate + Detect -> Generate -> Report
Output:
security-report.pdf— multi-page PDF booklet with up to 8 page types, mixed portrait/landscape orientation, full-bleed infographic pages
Step 1: Validate Prerequisites + Detect Artifacts
- Check Typst is installed:
- Run
which typstto verify Typst CLI is available - If not found, display:
TYPST NOT INSTALLED Typst is a modern typesetting system required for PDF generation. Install it for your platform: macOS: brew install typst Linux: cargo install typst-cli Windows: winget install typst Then re-run /security-report. - Halt if not installed.
- Run
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.
- 7d ago First seen · 272 lines · 83 tokens per session scan A f402a2c658a8
tachi.security-report is a command published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 25d ago), licensed Apache-2.0. It adds 83 tokens to every session and 3,140 once invoked, about $0.0004 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-08-30.
Other commands, from other repositories
fortigate
Run cs-security-analyst (AT + CA workflows) against the Fintech FortiGate zero-day scenario and produce a 7-task scorecard.
challenge
Run cs-security-analyst (AT workflow) against the Perfect Storm 8-vector crisis scenario and produce a 12-check mock comparison scorecard.
test
Run a USAP skill against the FortiGate zero-day test scenario and produce a 6-problem compliance scorecard.
run
Load a USAP skill SKILL.md and activate it as your operating persona. Argument: skill slug.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.