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 MuduiClaw/ClawKing --skill codebase-standardsgit clone --depth 1 https://github.com/MuduiClaw/ClawKingWrote 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/muduiclaw/clawking/codebase-standards)<a href="https://agentmods.dev/skills/muduiclaw/clawking/codebase-standards"><img src="https://agentmods.dev/badge/skills/muduiclaw/clawking/codebase-standards/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/muduiclaw/clawking/codebase-standards"><img src="https://agentmods.dev/badge/skills/muduiclaw/clawking/codebase-standards.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.00048 | $0.00787 |
| Opus 5.5 | $0.00019 | $0.00315 |
| Sonnet 5.5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
codebase-standards 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Standards — Skill
Adapted from Agent OS by Brian Casel. Auto-discover, index, and inject coding standards from any codebase. Plan products and shape feature specs with standards-aware context.
Available Commands
| Command | Trigger | Reference |
|---|---|---|
| Discover Standards | "discover standards", "extract conventions", "document patterns" | references/discover-standards.md |
| Inject Standards | "inject standards", "load standards", "apply conventions" | references/inject-standards.md |
| Index Standards | "rebuild index", "update standards index" | references/index-standards.md |
| Plan Product | "plan product", "define product", "product mission" | references/plan-product.md |
| Shape Spec | "shape spec", "plan feature", "spec out" | references/shape-spec.md |
How It Works
- Read the relevant reference file for the command being invoked
- Follow the reference instructions step by step
- Interact conversationally — ask the user questions directly (no special tools needed)
- Write files to the project's standards/product/specs directories
Workspace Conventions
All files are stored relative to the target project root (not the agent workspace):
{project}/
├── agent-os/
│ ├── standards/ # Discovered coding standards
│ │ ├── index.yml # Standards index for quick matching
│ │ ├── api/ # Standards by area
│ │ ├── database/
│ │ ├── frontend/
│ │ └── global/
│ ├── product/ # Product documentation
│ │ ├── mission.md
│ │ ├── roadmap.md
│ │ └── tech-stack.md
│ └── specs/ # Feature specifications
│ └── {YYYY-MM-DD-HHMM-feature-slug}/
│ ├── plan.md
│ ├── shape.md
│ ├── standards.md
│ └── references.md
If the project root is the current workspace ($HOME/clawd), files go in ./agent-os/. If working on a different project, ask the user for the project path first.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 68 lines · 48 tokens per session scan A 545eec96ccdb
codebase-standards is a skill published in the GitHub repository MuduiClaw/ClawKing (11 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 787 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-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…