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 agentmods add skills/clawdotnet/openclaw.net/docs-governancenpx skills add clawdotnet/openclaw.net --skill docs-governancegit clone --depth 1 https://github.com/clawdotnet/openclaw.netWrote 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/clawdotnet/openclaw.net/docs-governance)<a href="https://agentmods.dev/skills/clawdotnet/openclaw.net/docs-governance"><img src="https://agentmods.dev/badge/skills/clawdotnet/openclaw.net/docs-governance.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00388 |
| Opus 5 | $0.00009 | $0.00194 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
docs-governance 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 4d 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
Use this skill when creating, moving, or reorganizing Markdown documentation in this repository.
-
Documentation placement rules
- Put product, setup, architecture, operations, compatibility, roadmap, and engineering notes in
docs/. - Keep repository-standard meta files at the repo root only when the platform or community expects them there:
README.md,CHANGELOG.md,SECURITY.md,CONTRIBUTING.md,CODE_OF_CONDUCT.md, andLICENSE. - Keep Copilot and agent customization files where the tooling expects them:
AGENTS.md,.github/copilot-instructions.md, and.github/skills/**/SKILL.md. - Keep shipped OpenClaw runtime skills under
src/OpenClaw.Gateway/skills/<skill>/SKILL.md; do not move those intodocs/.
- Put product, setup, architecture, operations, compatibility, roadmap, and engineering notes in
-
Naming and structure rules
- Prefer
docs/<topic>.mdwith descriptive kebab-case names for new documentation. - If a topic grows, create a focused subfolder under
docs/rather than adding more root Markdown files. - Do not add general documentation to the repository root.
- Prefer
-
Change rules
- When moving or adding docs, update relative links in the same change.
- Update README quick links when the document is user-facing or operationally important.
- Do not move issue templates, pull request templates, licenses, or any
SKILL.mdfiles unless the task is specifically about those systems.
-
Default behavior
- If a new Markdown document is requested and no location is specified, place it in
docs/. - If a document mixes repository policy and product guidance, keep the policy file in its standard root location and move the product guidance into
docs/.
- If a new Markdown document is requested and no location is specified, place it in
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.
- 4d ago First seen · 26 lines · 18 tokens per session scan A 959ef509889a
docs-governance is a skill published in the GitHub repository clawdotnet/openclaw.net (488 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 388 once invoked, about $0.0001 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-30.
Other skills, from other repositories
datadesigner-docs
Maintain the NeMo Data Designer Fern docs site under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", "regenerate notebooks", "update dev note", any request that touches fern/.
review-code
Perform a thorough code review of the current branch or a GitHub PR by number.
create-pr
Create a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping).
update-pr
Update an existing GitHub PR description to reflect current changes after incorporating feedback.
commit
Commit current changes with a clear, descriptive message.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…