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 dashboardgit 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/dashboard)<a href="https://agentmods.dev/skills/akasecurity/ai-tc/dashboard"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/dashboard/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/dashboard"><img src="https://agentmods.dev/badge/skills/akasecurity/ai-tc/dashboard.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.00017 | $0.00287 |
| Opus 5.5 | $0.00007 | $0.00115 |
| Sonnet 5.5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
aka-dashboard 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 dashboard
Launch the AKA web dashboard and relay the short status the script prints as-is.
The command returns immediately: it starts the dashboard server in the background
and it opens in the browser once ready, so a lack of further output is not an
error — do not wait on it or re-run it. If the script prints install guidance (the
aka CLI isn't installed), relay that verbatim.
If the user asked for a specific port, pass --port <N> through unchanged;
otherwise run it with no arguments.
node "${PLUGIN_ROOT}/scripts/dashboard.js" [--port <N>]
This mirrors the aka dashboard CLI command: it serves the OSS web-ui against
your local store at ~/.aka/data (no backend) and opens
http://localhost:4319/security. The web server is bundled in the
@akasecurity/cli package — the plugin ships no server of its own — so the
launcher delegates to the aka CLI and, if it isn't installed, prints how to get
it. For the terminal-only read surfaces, use the aka-health, aka-findings,
aka-recommend, aka-audit, or aka-tokens skills instead.
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 · 28 lines · 17 tokens per session scan A 37b05852395a
aka-dashboard is a skill published in the GitHub repository akasecurity/ai-tc (13 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 287 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.