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 lahkiri/xeo-forge --skill governance-inheritancegit clone --depth 1 https://github.com/lahkiri/xeo-forgeWrote 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/lahkiri/xeo-forge/governance-inheritance)<a href="https://agentmods.dev/skills/lahkiri/xeo-forge/governance-inheritance"><img src="https://agentmods.dev/badge/skills/lahkiri/xeo-forge/governance-inheritance/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/lahkiri/xeo-forge/governance-inheritance"><img src="https://agentmods.dev/badge/skills/lahkiri/xeo-forge/governance-inheritance.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.00056 | $0.00241 |
| Opus 5 | $0.00028 | $0.00120 |
| Sonnet 5 | $0.00011 | $0.00048 |
| Haiku 4.5 | $0.00006 | $0.00024 |
Grade A, and why
governance-inheritance 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.
What it actually says
New Xeo Forge capabilities never create their own permission path. When the agent adds a feature that acts on the workspace, network, or host — subagent delegation, sandbox tiers, browser control, anything future capabilities share — it routes that capability's decisions through the existing PermissionRule engine: classifyToolCall gains a case, the per-level AUTONOMY_RULES gain their rows as data, and dispatch runs through the same authorizeToolCall gate every other tool answers to.
If a new capability seems to need an exception from the rule engine, the agent stops and widens the rule vocabulary instead (a new action type or resource prefix, expressed as data with an audit note). The agent never hardcodes an if that decides permission by capability identity. Subagent children inherit the parent's rule set verbatim — a delegated actor holding broader authority than its parent is treated as a security defect, not a convenience.
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 · 9 lines · 56 tokens per session scan A fffdfd9db468
governance-inheritance is a skill published in the GitHub repository lahkiri/xeo-forge (11 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 241 once invoked, about $0.0003 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
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
tmux-lane-orchestrator
Manage one tmux agent lane from its matching ops pane, inspect live pane state and Codex logs on cold start, and produce concise manager summaries for OpenClaw and adjacent project work.
ghcrawl-cluster-operator
Use when inspecting a ghcrawl SQLite store, pulling GitHub issue/PR data, refreshing summaries, embeddings, and clusters, or extracting one cluster and its evidence through the ghcrawl CLI.
opik-optimizer
Optimize LLM prompts, tools, and agents in Opik using standardized optimizer workflows (prompt optimization, tool optimization, and parameter tuning), dataset/metric wiring, and result interpretation.
crabpot-perf-metrics
Interpret Crabpot and OpenClaw performance dashboard metrics, import-loop profiles, runtime profiles, and branch-to-branch perf deltas without over-reading noisy samples.
org-branch-cleanup
Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…