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 Firstp1ck/pi-coding-agent-forge --skill subagent-governancegit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-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/firstp1ck/pi-coding-agent-forge/subagent-governance)<a href="https://agentmods.dev/skills/firstp1ck/pi-coding-agent-forge/subagent-governance"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/subagent-governance/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/firstp1ck/pi-coding-agent-forge/subagent-governance"><img src="https://agentmods.dev/badge/skills/firstp1ck/pi-coding-agent-forge/subagent-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 110 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00074 | $0.03567 |
| Opus 5.5 | $0.00030 | $0.01427 |
| Sonnet 5.5 | $0.00015 | $0.00713 |
| Haiku 4.5 | $0.00007 | $0.00357 |
Grade A, and why
subagent-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 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent Governance
Use this skill in the parent orchestrator session before delegating work to child agents, before replacing a child that did not deliver, and when accepting delegated results. It decides which delegation shapes are allowed and which evidence is required. It is guidance, not a runtime guard: loading it does not install a package, enable an integration, change settings, or block a tool call.
Scope and Boundary
- This skill controls admissibility. Whether delegation is allowed at all, how many children of which kinds may be declared, who may write, what a worker must be told, what a handoff must return, when a replacement launch is legal, and how a reviewer finding is dispositioned.
- The harness's delegation documentation controls runtime mechanics. Tool schemas, action names, launch/monitor/wait syntax, context modes, agent and chain authoring, configuration, and error handling. In Pi, the installed
pi-subagentsskill remains canonical for those mechanics; this skill does not restate, replace, or override it, and it is not a second mechanics reference. - Parent-only. Do not inject or follow this skill inside a spawned child. A child does not own delegation, fanout, integration, or completion decisions. The one exception is a child that the parent explicitly assigned bounded fanout; it stays inside that assignment.
- Admissibility and runtime success are independent. An admissible shape can still fail at runtime, and no runtime capability, convenience command, or saved workflow makes a noncompliant shape admissible.
When to Use
Use when the parent is deciding whether to delegate, what to declare in a delegation request, how to keep concurrent work safe, how to react to a failed or partial delegated run, or what to do with reviewer output.
Do not use for:
- Launch syntax, tool arguments, action names, context modes, scheduling, or error messages — those belong to the harness's mechanics documentation.
- Creating, editing, disabling, or ejecting agents and saved workflows.
- Cost, usage, or status inspection with no pending delegation decision.
- Work the parent should simply do itself, such as a direct edit, a direct answer, or a single-file fix.
- Feature scope, plan structure, completion gates, or report obligations, which belong to the feature workflow policy in use.
What ships with it
4 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 · 189 lines · 74 tokens per session scan A 287d690eb980
subagent-governance is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (91 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 3,567 once invoked, about $0.0003 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
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.
colab-finetuning
Fine-tune LLMs on Google Colab GPUs directly from openscience. Connects to Colab runtimes via WebSocket bridge for remote training with Unsloth. Supports SFT, GRPO, DPO, vision, and TTS workflows on free T4 to Pro A100 GPUs.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…