Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/akasecurity/ai-tc/detectionsgit clone --depth 1 https://github.com/akasecurity/ai-tcWrote 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/akasecurity/ai-tc/detections)<a href="https://agentmods.dev/commands/akasecurity/ai-tc/detections"><img src="https://agentmods.dev/badge/commands/akasecurity/ai-tc/detections.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.00011 | $0.00319 |
| Opus 5 | $0.00005 | $0.00160 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
detections 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.
What it actually says
AKA detections
Run the read script and show the user its output exactly as printed. The script already prints its content inside a Markdown code fence — reproduce that verbatim and do not add another code fence, strip the fence, or reformat it. The fence is required: it is a space-aligned monospace table that Markdown would otherwise collapse. Do not reformat the columns or restate each row.
node "${CLAUDE_PLUGIN_ROOT}/scripts/query.js" detections
This lists the detection packs installed in ~/.aka/data/aka.db — one row per
pack with its installed version, the latest version this plugin ships, rule
count, enabled state, assigned enforcement policy, and whether an update is
available. These packs are what the plugin actually scans with.
Detection updates are never applied automatically — a plugin upgrade only records what's newly available; the installed packs keep running unchanged until the user updates them. This command is strictly read-only: do not apply, enable, disable, or re-policy a detection from here. If the user wants to update, tell them to run one of these themselves in a terminal:
aka detections update --all— update every packaka detections update <pack-id>— update one packaka dashboard→ Detections → Update — review and apply in the dashboard
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 · 31 lines · 11 tokens per session scan A 8deebe87cc2c
detections is a command published in the GitHub repository akasecurity/ai-tc (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 319 once invoked, about $0.0001 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-31.
Other commands, from other repositories
address
Address code review feedback — corroborate, validate, and implement changes from a review's final.md.
translate-review-to-single-human
Translate a multi-reviewer code review into a single human-voice GitHub PR comment.
map
Generate a Code Review Map to help navigate large, complex changesets.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
fleet
Show the Fleet Deck board URL and a live summary of every Claude Code session on this machine.