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 pilotspace/pilot-space --skill generate-pm-blocksgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/generate-pm-blocks)<a href="https://agentmods.dev/skills/pilotspace/pilot-space/generate-pm-blocks"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/generate-pm-blocks/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/pilotspace/pilot-space/generate-pm-blocks"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/generate-pm-blocks.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.00027 | $0.02404 |
| Opus 5.5 | $0.00011 | $0.00962 |
| Sonnet 5.5 | $0.00005 | $0.00481 |
| Haiku 4.5 | $0.00003 | $0.00240 |
Grade A, and why
generate-pm-blocks 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 2mo 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PM Blocks Skill
Generate structured PM blocks from natural language descriptions. Analyzes user input to determine which block types are appropriate and inserts them into the active note.
Quick Start
Use this skill when:
- User requests PM block creation (
/generate-pm-blocks) - Planning sprints, projects, or milestones
- Setting up risk registers, decision records, or RACI matrices
- User describes a workflow that maps to multiple PM block types
Example:
User: "Set up sprint planning with timeline, risk register, and RACI matrix for our API migration"
AI calls create_pm_block 3 times:
1. create_pm_block(block_type="timeline", data={...}, after_block_id=null)
2. create_pm_block(block_type="risk", data={...}, after_block_id=<prev_block_ref>)
3. create_pm_block(block_type="raci", data={...}, after_block_id=<prev_block_ref>)
AI responds: "[RECOMMENDED] Inserted 3 PM blocks: Timeline with 4 milestones, Risk Register with 3 risks, and RACI Matrix for 3 deliverables."
Workflow
-
Parse Description
- Identify which block types the user needs from keywords:
- Decision: "decide", "choice", "option", "evaluate", "pros/cons"
- Form: "survey", "collect", "questionnaire", "feedback", "form"
- RACI: "responsibility", "accountable", "who does what", "roles", "RACI"
- Risk: "risk", "mitigation", "threat", "vulnerability", "impact"
- Timeline: "timeline", "milestones", "schedule", "deadline", "phases"
- Dashboard: "metrics", "KPIs", "tracking", "progress", "dashboard"
- If no specific type is mentioned, infer from context (e.g., "sprint planning" implies timeline + risk)
- Identify which block types the user needs from keywords:
-
Generate Block Data
- For each identified block type, construct the data object following the schemas below
- Use meaningful, context-specific content derived from the user's description
- Generate realistic IDs (e.g.,
m-1,r-1,w-1,f-1,o-1,d-1)
-
Insert Blocks Sequentially
- Call
create_pm_blockfor each block type as a SEPARATE tool call - Use
after_block_idfrom the previous insertion to maintain ordering - Users see each block appear progressively
- Call
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.
- 2mo ago First seen · 255 lines · 27 tokens per session scan A caf4ab8a6076
generate-pm-blocks is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,404 once invoked, about $0.0001 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…