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 ndisisnd/msg --skill plan-emgit clone --depth 1 https://github.com/ndisisnd/msgWrote 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/ndisisnd/msg/plan-em)<a href="https://agentmods.dev/skills/ndisisnd/msg/plan-em"><img src="https://agentmods.dev/badge/skills/ndisisnd/msg/plan-em/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/ndisisnd/msg/plan-em"><img src="https://agentmods.dev/badge/skills/ndisisnd/msg/plan-em.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.00178 | $0.01829 |
| Opus 5.5 | $0.00071 | $0.00732 |
| Sonnet 5.5 | $0.00036 | $0.00366 |
| Haiku 4.5 | $0.00018 | $0.00183 |
Grade A, and why
plan-em 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-em
This file is a router. The five-step protocol lives in refs/protocol-em.md and the team-lane fan-out in refs/protocol-team.md — neither is restated here.
Usage
Invoke: /plan-em <prd-path>. The PRD path is a .md file inside a PRD folder in any lane — features/{planned,wip,done}/prd-[n]-[slug]/ or the legacy flat features/prd-[n]-[slug]/.
- Slash command:
/plan-em· natural language: "engineering plan for ", "scope this PRD", "spin up eng agents" · context: a path to an existing approved PRD.mdfile, typically passed forward fromplan-pmorplan-review /plan-em <prd-path> --quiet/--status <n>m— suppress or retune this run's status heartbeat; flag beats policy beats default (../shared/refs/status-heartbeat.md)
Hard refusals:
- Invocation without a PRD path: refuse. State that
plan-emrequires an existing PRD. Offer two paths: run/plan-pmto create one, or supply a path to an existing PRD.mdfile. - PRD path does not exist or does not match a lane-lifecycle path —
features/{planned,wip,done}/prd-*/prd-*.md(top-level) orfeatures/{planned,wip,done}/prd-*/prd-*/prd-*.md(nested sub-PRD, perplan-pm's § Sub-PRD mode) — or the legacy flatfeatures/prd-*/prd-*.md/features/prd-*/prd-*/prd-*.md: refuse. State the expected location.
Execution mode
Two mutually exclusive execution lanes — --team is the default. The flag changes
only how the wave is dispatched at Step 4; every other step is identical in both lanes.
| Flag | Lane | Step 4 dispatch |
|---|---|---|
--team (default) |
Team | one orchestrator engineer agent on Opus decomposes the wave below the roster/stack level into file-disjoint, model-tiered packets and fans them out to leaf eng subagents. |
--solo |
Solo | one leaf eng subagent per roster stack, whole-stack scope each, on the inherited model. |
In --team mode plan-em is a thin dispatcher: it spawns the orchestrator
backgrounded as one watched leaf and relays its REPORT blocks; run-ids stay disjoint
(emteam-<epoch> vs em-<epoch>) — mechanics in refs/protocol-em.md Step 4 +
../shared/refs/status-heartbeat.md § Relaying across a subagent boundary. The mode is a
persisted preference, not just a per-run flag (refs/protocol-em.md Step 0; pref file: ../shared/refs/exec-mode-pref.md).
What ships with it
3 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 · 100 lines · 178 tokens per session scan A fb0f5fb6f539
plan-em is a skill published in the GitHub repository ndisisnd/msg (6 stars, last pushed 2d ago), licensed MIT. It adds 178 tokens to every session and 1,829 once invoked, about $0.0007 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 skills, from other repositories
skillspec-migrate
Complete a .agent.partial file by resolving TODO markers.
skill-writer
Review a SkillSpec .agent file for quality, correctness, and adherence to SkillSpec design principles.
skillspec-test
Execute test blocks from a SkillSpec .agent file.
skillspec-backport
Reconcile changes from a modified SKILL.md back into the .agent source file.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent. Use when a pipeline conductor session is seeded, inspected or debugged. You MANAGE one issue/PR pipeline on one repo: two columns per item (session working? item solved?), send intent, never re-derive a red yourself.
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.