Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add akasecurity/ai-tc/plugin install akaWrote 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/setup)<a href="https://agentmods.dev/commands/akasecurity/ai-tc/setup"><img src="https://agentmods.dev/badge/commands/akasecurity/ai-tc/setup/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/commands/akasecurity/ai-tc/setup"><img src="https://agentmods.dev/badge/commands/akasecurity/ai-tc/setup.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.13136 |
| Opus 5.5 | $0.00007 | $0.05254 |
| Sonnet 5.5 | $0.00003 | $0.02627 |
| Haiku 4.5 | $0.00002 | $0.01314 |
Grade C, and why
setup scanned grade C with 3 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 2d 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.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
`.netrc`, `.pgpass`, `.git-credentials`, `.npmrc`, `.aws/credentials`, Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/akasecurity/ai-tc/bin-latest/tools/installer/install.sh | sh Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/akasecurity/ai-tc/bin-latest/tools/installer/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 992 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AKA setup wizard
You are onboarding the AKA Security plugin for this machine. AKA works
fully locally with zero backend and zero Docker: detection runs in-process
and findings persist to a local SQLite store at ~/.aka/data/aka.db.
This wizard tells a calibration story: introduce AKA → show what it does → offer one retroactive scan → report the real numbers it found and the posture it recommends → apply on confirmation → show the installed summary → hand off to the dashboard. Everything the user sees is derived from their actual history — never a fabricated or demo number. When there isn't enough history to judge, the wizard falls back to a conservative severity-derived floor instead of guessing.
The false-positive/severity judgment needs the raw (unmasked) findings to rate
them accurately, so it sends them to the model API through separate claude
CLI subprocesses (a large history is judged in several batches). Per finding it
sends the raw value; about 120 characters of the surrounding transcript
text on either side of it, re-scanned first so every secret AKA's rules detect
in that window is masked — including the finding's own value where it appears
there, which leaves the raw value itself as the only raw text that crosses; and
the finding's non-sensitive labels (rule id, category, severity, the masked
value, the confidence score, and a counter the model echoes back). The source
transcript's path never crosses. Those subprocesses ask the claude CLI to
write no transcript, so the raw values do not enter this conversation or your
scannable history — but a copy of them does leave the machine, sent to the
model provider like any other Claude prompt. You act only on the raw-free plan
the subprocesses print back.
That send takes two separate consents, collected at two different points and neither implying the other: the historical-read grant in step 1 (may AKA read past transcripts at all) and the model-judge grant in step 3 (may what it found be sent to the model API). Each is stated plainly before its own picker, and the judge refuses to run without the step-3 grant. The vault grant in step 1b is a third, separate question about local custody — it authorizes no send, and nothing about it changes what leaves the machine.
Follow the steps below in order. Nothing is written to the policy store until step 5 (or a floor fallback in step 3 if the calibration can't complete).
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.
- 2d ago Changed · +58 lines scan B → C 73db3469fe1f
- 12d ago Changed · +11 lines 222cf99f9a41
- 1mo ago Changed · +28 lines 85ced8f7023a
- 1mo ago First seen · 895 lines · 17 tokens per session scan B cd85739675d1
setup is a command published in the GitHub repository akasecurity/ai-tc (11 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 13,136 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 3 findings (reaches for credential files, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
fleet
Show the Fleet Deck board URL and a live summary of every Claude Code session on this machine.
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.