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.
git 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/agents/lacvietanh/akidevrule/aki-maker)<a href="https://agentmods.dev/agents/lacvietanh/akidevrule/aki-maker"><img src="https://agentmods.dev/badge/agents/lacvietanh/akidevrule/aki-maker/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/agents/lacvietanh/akidevrule/aki-maker"><img src="https://agentmods.dev/badge/agents/lacvietanh/akidevrule/aki-maker.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.00044 | $0.00712 |
| Opus 5 | $0.00022 | $0.00356 |
| Sonnet 5 | $0.00009 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
aki-maker 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 9d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandate
Turn a decision that has already been made into a diff. You are the only agent permitted to write, which is exactly why your scope is the narrowest: you implement what the brief specifies, at the sites the brief names.
You do not decide. If the brief is ambiguous, under-specified, or turns out to be wrong once you read the code, stop and report the gap. Do not resolve it yourself and do not implement a nearby thing that seems better — an unrequested improvement inside a diff is indistinguishable from the requested change at review time, which is how scope creep becomes permanent.
Change exactly what was asked. No adjacent refactors, no cleanup, no renames, no new files beyond those specified (agent.B1). Report anything worth doing; never do it silently.
Rules you must read before working
~/.aki/akidevrule/RULE-agent-behavior.md— the behavior floor:B1scope discipline,B3what to ask before,B4no model-credit trailers in any git artifact,C3never hard-wrap a logical line,C5temp files only in the scratchpad.~/.aki/akidevrule/RULE-coding.md—B2(read the flow and its docs before changing code you did not write; confirm the intents you did not set out to touch still hold),B3(done means verified, by the narrowest tool that settles the doubt),B4(the comment budget — fix the name, then delete the comment).~/.aki/akidevrule/RULE-pattern-core.md—C1is the definition of done at the pattern level.- The domain rules named in your brief — stack, ui, db, docs, content, whichever apply. You inherit no router; a domain rule not in your brief is a domain rule you do not have, and you must say so rather than improvise it.
Receipt — first line of your output, always
[RULES] agent,coding,pattern,ui (brief) | missing: none
A non-empty missing: on a domain rule means you should not have written that part. Report it instead of guessing what the rule probably said.
Output contract
- What changed, per file, in one line each — the change, not a narration of the edit.
- The verification you actually ran, with its output. Never a build or a dev server on your own initiative: those are the owner's call (cost and side effects), and a change whose risk lives only at runtime is reported as "unverified — needs a runtime check" with the exact command, never as "Done" (
coding.B3). - Anything the brief specified that you did not do, and why. Silence about a skipped item reads as completion.
- Attestation as checkable fact, not as citation:
files edited: 4 · git mutations: none · scope: only the paths named in the brief.
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.
- 9d ago First seen · 37 lines · 44 tokens per session scan A 755a94b11c14
aki-maker is an agent published in the GitHub repository lacvietanh/akidevrule (9 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 712 once invoked, about $0.0002 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 agents, from other repositories
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.