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.compensating-controls.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.compensating-controls)<a href="https://agentmods.dev/commands/davidmatousek/tachi/tachi.compensating-controls"><img src="https://agentmods.dev/badge/commands/davidmatousek/tachi/tachi.compensating-controls.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.00041 | $0.02042 |
| Opus 5 | $0.00020 | $0.01021 |
| Sonnet 5 | $0.00008 | $0.00408 |
| Haiku 4.5 | $0.00004 | $0.00204 |
Grade A, and why
tachi.compensating-controls 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 — 194 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 Flags
-
If
$ARGUMENTScontains--target <path>:- Set
target_pathto the specified path - Strip
--target <path>from$ARGUMENTS(trim extra whitespace)
- Set
-
Default:
target_path = "."(current working directory) -
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(outputs written to same directory as input risk-scores) -
Remaining
$ARGUMENTSis treated as the risk-score input directory path. -
If no input 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 containsrisk-scores.mdorrisk-scores.sarif. Setinput_dirto that path and display:Auto-detected input: {input_dir}. - Otherwise, default to current working directory (
.).
- If
Overview
Single-command entry point for tachi compensating controls analysis — the third link in the pipeline: /threat-model → /risk-score → /compensating-controls. Validates prerequisites, locates risk score input and target codebase, invokes the control-analyzer agent, and writes dual-format output files.
Flow: Validate → Locate Input → Analyze Controls → Report
Output suite:
compensating-controls.md— Coverage matrix, control details with file:line evidence, recommendations, residual risk summarycompensating-controls.sarif— SARIF 2.1.0 with per-finding residual scores, control properties, and preserved fingerprints
Step 1: Validate Prerequisites
- Check tachi agents are installed:
- Verify
.claude/agents/tachi/control-analyzer.mdexists - If missing, display:
TACHI CONTROL ANALYZER NOT INSTALLED Run: cp -r <tachi-repo>/adapters/claude-code/agents/control-analyzer.md .claude/agents/tachi/ See: https://github.com/davidmatousek/tachi - Halt if missing.
- Verify
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 · 194 lines · 41 tokens per session scan A 2e8631032b4b
tachi.compensating-controls is a command published in the GitHub repository davidmatousek/tachi (90 stars, last pushed 25d ago), licensed Apache-2.0. It adds 41 tokens to every session and 2,042 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-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.