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/scangit 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/scan)<a href="https://agentmods.dev/commands/akasecurity/ai-tc/scan"><img src="https://agentmods.dev/badge/commands/akasecurity/ai-tc/scan.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 | $0.00009 | $0.00697 |
| Opus 5 | $0.00005 | $0.00349 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
scan 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AKA scan
Single-repo scan (default)
Run the worktree scan 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 space-aligned monospace that Markdown would otherwise collapse.
node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --dir "${PWD}"
This scans all source files (.ts, .js, .py, .java, .rb, .cs, .go,
.rs, .php, and more) under the current project directory for insecure code
patterns — SQL injection, command injection, XSS, insecure deserialization, weak
cryptography, hardcoded credentials, dev-mode configuration leaks, and other
OWASP Top 10 issues.
Results are recorded to the local store (~/.aka/data/aka.db) and are visible
via /findings. Re-running /aka:scan is safe — files whose content has already
been recorded are skipped.
Files excluded by the repo's .gitignore are still scanned — local scratch
and generated files are a common place for real secrets to hide — but their
findings are marked as coming from gitignored content and reported as
informational in the summary.
To exclude paths from scanning entirely, add a .akaignore file (gitignore
syntax, any directory level). Unlike .gitignore, .akaignore is a hard
skip: matching files are never read and produce no findings. A negation also
re-includes a directory the scanner skips by default — e.g. !vendor/ scans
first-party code living under vendor/.
Multi-repo scan (opt-in)
To scan all git repositories found under the current directory (up to 4
directory levels deep), use the --discover flag:
node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --discover
To search from a different directory, pass --root (and optionally --depth):
node "${CLAUDE_PLUGIN_ROOT}/scripts/filescan.js" --discover --root ~/projects --depth 3
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.
- 4d ago First seen · 70 lines · 9 tokens per session scan A e84f60265177
scan is a command published in the GitHub repository akasecurity/ai-tc (10 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 697 once invoked, about $0.0000 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
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.