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 findingsgit 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/findings)<a href="https://agentmods.dev/skills/akasecurity/ai-tc/findings"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/findings/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/findings"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/findings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00250 |
| Opus 5.5 | $0.00006 | $0.00100 |
| Sonnet 5.5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
aka-findings 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 1mo 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 findings
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.
If the user asked to filter by severity — e.g. --critical, --high,
--medium, --low, or --severity <level> — pass that flag through to the
script unchanged. Otherwise run it with no flag.
node "${PLUGIN_ROOT}/scripts/query.js" findings [--severity <critical|high|medium|low>]
This lists the most recent findings from ~/.aka/data/aka.db with their rule,
category, severity, action taken, and the masked match (raw secrets are
never stored), narrowed to one severity when a filter is given. It is read-only.
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.
- 1mo ago First seen · 25 lines · 15 tokens per session scan A bb391af1a967
aka-findings is a skill published in the GitHub repository akasecurity/ai-tc (13 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 250 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.