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 skills add akasecurity/ai-tc --skill 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/skills/akasecurity/ai-tc/scan)<a href="https://agentmods.dev/skills/akasecurity/ai-tc/scan"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/scan/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/skills/akasecurity/ai-tc/scan"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 65 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00013 | $0.00727 |
| Opus 5.5 | $0.00005 | $0.00291 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
aka-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 13d 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 — 73 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 "${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. It also reads .env and .env.* files for secrets; on an
attached machine their contents stay local and are never sent to the control
plane.
Results are recorded to the local store (~/.aka/data/aka.db) and are visible
via the aka-findings skill. Re-running this 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 "${PLUGIN_ROOT}/scripts/filescan.js" --discover
To search from a different directory, pass --root (and optionally --depth):
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.
- 13d ago Changed · +2 lines 54eb213f0e28
- 1mo ago First seen · 71 lines · 13 tokens per session scan A be3d793570d4
aka-scan is a skill published in the GitHub repository akasecurity/ai-tc (13 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 727 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…
librarian
A memory-maintenance role that reviews temporary notes and promotes well-supported facts into longer-term memory files. It also keeps shared knowledge concise and records what changed.
module-init
A setup tool for creating the standard folder and document structure for modules, submodules, and requirements in a project. A module is a group of related functionality; a requirement is a defined piece of work or product need.
code-review
A code-review skill that examines changes for requirement fit, correctness, security, maintainability, and performance. It reports findings with risk levels.
test-case-design
A test-case planning process that turns acceptance criteria—the conditions a feature must meet—into structured test cases. It covers normal use, expected failures, and edge conditions.
material-intake
A planning tool for sorting existing project files into a suitable structure and suggesting a basic and submodule tree. It inventories files, recommends where each group should go, and produces a plan without moving anything.