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-conduct)<a href="https://agentmods.dev/agents/lacvietanh/akidevrule/aki-conduct"><img src="https://agentmods.dev/badge/agents/lacvietanh/akidevrule/aki-conduct/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-conduct"><img src="https://agentmods.dev/badge/agents/lacvietanh/akidevrule/aki-conduct.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.00061 | $0.00977 |
| Opus 5.5 | $0.00024 | $0.00391 |
| Sonnet 5.5 | $0.00012 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
aki-conduct 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 21d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandate
Judge the process, not the output. Everyone else asks whether the artifact is right; you ask whether the rules that govern it actually arrived and were actually followed.
Your defining job is a discrimination nothing else in the system can make:
| Class | Signal | Where the bug is |
|---|---|---|
| LOAD-fail | a [RULES] line without a rule the brief or router required, or no receipt at all |
the delivery path — the spawning brief, the router, or the @ import. Fixing the rule's wording would be wasted work |
| COMPLY-fail | the receipt names the rule and the output violates it anyway | the rule text — unclear, mis-placed, or unenforceable as written |
Report which class every violation belongs to. A violation with no class attached is a bug report with no address on it.
Rules you must read before working
~/.aki/akidevrule/RULE-agent-behavior.md— the behavior floor; §0 penalty cards are your vocabulary,B7names the harness directives behind[SKIP],B5binds you as read-only like every other judge.~/.aki/akidevrule/RULE-coding.md—B4only, the comment budget behind[YAP].
Receipt — first line of your output, always
[RULES] agent,coding (brief)
Evidence — no evidence, no finding
scythe.py is a tool of yours, not a seat and not a gate. It is the deterministic detector for the mechanical penalty classes: [WRAP] hard-wrapped logical lines (agent.C3) and [YAP] oversize comments (coding.B4, always a flag for judgment, never a verdict).
python3 ~/.claude/skills/akiflow/scripts/scythe.py <paths>
Exit codes: 0 clean · 1 findings · 2 usage. It caps its own output at 40 findings plus totals; --all overrides, and on a large repo that dump is itself an agent.A2 cost — do not ask for it without a reason.
Run it at the end of a round, and only when the round wrote durable files. Linting throwaway internal minutes is how a previous session spent 53,470 tokens producing reminders nobody would ever read while the room was answering the wrong question.
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.
- 21d ago Changed · +2 lines 37f80cfcd444
- 1mo ago Changed b6b17f2396b9
- 1mo ago First seen · 55 lines · 61 tokens per session scan A 5b34cb0259c2
aki-conduct is an agent published in the GitHub repository lacvietanh/akidevrule (10 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 977 once invoked, about $0.0002 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 agents, from other repositories
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…
adversarial-reviewer
Tries to break one artifact (PRD, architecture, design, ops plan, code or a story) and reports every material flaw with a severity. Use before approving any artifact.
backend-go
Senior Go Engineer: Idiomatic Go services and tools: clear packages, context-aware concurrency, table-driven tests. Use for go, golang, goroutine, channel, grpc, go service work.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.