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 lacvietanh/akidevrule --skill akihelpgit clone --depth 1 https://github.com/lacvietanh/akidevruleWrote 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/lacvietanh/akidevrule/akihelp)<a href="https://agentmods.dev/skills/lacvietanh/akidevrule/akihelp"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akihelp/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/lacvietanh/akidevrule/akihelp"><img src="https://agentmods.dev/badge/skills/lacvietanh/akidevrule/akihelp.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.00096 | $0.02171 |
| Opus 5 | $0.00048 | $0.01086 |
| Sonnet 5 | $0.00019 | $0.00434 |
| Haiku 4.5 | $0.00010 | $0.00217 |
Grade A, and why
akihelp 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
akihelp — live introduction to the Aki system
Invoke with /akihelp, or when the user asks what's available in this setup ("what can this do", "hệ thống Aki có gì", "how do I use this", "what skills do I have"). Goal: give the user a clear, accurate picture of the whole Aki Claude Code system so they can fully exploit it.
This skill must never go stale. Do not hardcode a skill/rule inventory in this file — read live state every time it runs, so the output is always correct even after install.sh adds, renames, or removes something.
Steps
-
Read
~/.aki/akidevrule/index.md— the file manifest with tiers and purposes. -
List
~/.claude/skills/and read the frontmatter (name+description) of each skill whose directory is prefixedaki— these are the installed Aki skills. -
List
~/.claude/agents/and read the frontmatter (name/description/tools/model) of each file prefixedaki-— these are the installed Aki agent definitions. The directory is shared with the user's own agents, so introduce only theaki-ones. If the directory does not exist, that layer is simply not installed: drop the section rather than describing it. -
Render a compact overview with these sections:
- Skills (active, user-invoked) — one row per aki-skill: its
/name, its one-line description (from frontmatter), and when to reach for it. - Agent definitions (who the work gets handed to) — one row per installed
aki-agent from step 3: what it is for, and the property that is mechanical rather than promised (itstools:list, which is what makes a read-only agent actually read-only, and itsmodel:, so a tier is never improvised). Say the thing people get wrong: this is a catalog, not a roster — an agent is spawned because a specific requirement needs it, never because it exists. - Passive system (akirule) — explain the 3 tiers: Core rules always loaded every turn; Contextual/Analytical rules auto-loaded on signal match; full load via an explicit phrase ("nạp full", "load all rules"). Note that
akiruleitself is hidden from the/menu by design (user-invocable: false) — it runs passively, not as a command. - One brain, two modes —
METHOD-deep-think.mdis read passively by akirule inside normal tasks (brief, inline, at most one clarifying question) and actively by/akithink(full 5-phase interactive session for big/hard-to-reverse/goal-ambiguous decisions). Short version of the comparison, not the full METHOD text. - Editing rules — this whole system is generated from a source repo (akidevrule); the installed copies under
~/.aki/akidevruleand~/.claudeare deployed output, never edited directly. Changes go through the source repo +install.sh. Note for context: the same skill corpus (not the rule corpus) is also synced byinstall.shto Antigravity/Gemini and to Codex, Kiro, and Grok CLIs on this machine if present — this skill itself only introduces the Claude Code side.
- Skills (active, user-invoked) — one row per aki-skill: its
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.
- 12d ago First seen · 48 lines · 96 tokens per session scan A 55ffbc18061d
akihelp is a skill published in the GitHub repository lacvietanh/akidevrule (9 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 2,171 once invoked, about $0.0005 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 skills, from other repositories
starfleet-tasks
Task capture, task lifecycle, dashboard topics, and reports via starfleetctl. Load when capturing, working on, or reporting a task, and for all dashboard access.
starfleet-timer
Set timers instead of blocking a session with sleep/watch-loops (e.g. waiting for a GitHub Actions run): the timer fires a comms directive into the fleet at the scheduled time, and the poller injects it into the owning ship's next turn — no background process, no blocking, survives a session restart.
starfleet
Fleet coordination core — comms, board status, concurrency/isolation, and pointers to the themed starfleet- skills. Load when handling inter-ship messages, checking the board, or unsure which starfleet skill applies.
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.
starfleet-sessions
Ship session and workspace management — spawning ships, session attach/stop, git worktrees, web console, deployment. Load when launching/administering ships or managing the fleet web console.
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…