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 perniemann/pnCore --skill pn-create-workflow-roadmapgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-create-workflow-roadmap)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-create-workflow-roadmap"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-create-workflow-roadmap/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/perniemann/pncore/pn-create-workflow-roadmap"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-create-workflow-roadmap.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.00044 | $0.01811 |
| Opus 5 | $0.00022 | $0.00905 |
| Sonnet 5 | $0.00009 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
pn-create-workflow-roadmap 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Workflow Roadmap
Purpose
Generate docs/WORKFLOW.md — a project execution guide that maps every phase from the implementation plan to specific pn-core commands, recommends model tiers per step, and estimates token costs. Enables cost-aware project planning and session management.
When to use
- After pn-writing-plans completes and the plan document exists
- During pn-new (Involved mode), after plan and before skeptic review
- When user requests a workflow roadmap, execution guide, or cost estimate for a planned build
Announce at start: "I'm using pn-create-workflow-roadmap to generate the project workflow."
Before drafting: Load get_skill("pn-documentation") and apply the WORKFLOW roadmap format.
Input
- Plan document:
docs/plans/YYYY-MM-DD-<feature>.md(required) - Discovery spec:
docs/discovery/YYYY-MM-DD-<slug>.md(required) - Prior-art research:
docs/research/YYYY-MM-DD-<slug>-prior-art.md(when it exists) - Ref docs: Prefer
docs/refs/PRD.md,docs/refs/DESIGN-DOC.md, etc.
Instructions
1. Read inputs
Read the plan document, discovery spec, and any ref docs. Extract:
- Project name
- Delivery tier (MVP or full)
- Phase list with tasks per phase
- Stack and scope from discovery
- Security and design requirements that affect model tier selection
2. Map phases to commands
For each phase in the plan, determine which pn-core commands/skills run at each step. Use the plan's task descriptions, file types, and scope to select:
| Task type | Command/Skill |
|---|---|
| Scaffold, project init | pn-scaffolder |
| Frontend components, pages, routes | pn-frontend-developer |
| Backend API, DB, auth | pn-backend-developer |
| Tests | pn-testing-specialist |
| Asset creation (logo, icons, illustrations) | pn-assets-manager |
| Generative media (ComfyUI, T2V, cinematic pipelines) | pn-generative-media-director |
| Design system, visual polish | pn-design |
| Game mechanics, progression | pn-game |
| Security audit, GDPR, RLS | pn-security-auditor |
| Accessibility audit, Lighthouse | pn-frontend-audit |
| Code review, quality gates | pn-reviewer |
| Acceptance verification + delivery | pn-deliver |
| Doc updates | pn-document |
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 · 160 lines · 44 tokens per session scan A aac750826a90
pn-create-workflow-roadmap is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 1,811 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
plan
Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present), invokes Coco native plan mode as a mandatory gate, captures the approved plan to plan.md, creates initial flow.json template, and commits. Must have $spec completed first.
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
ops-dora
CocoOps DORA metrics — computes four DORA-adapted delivery metrics from Snowflake task history and git log. Extends the longitudinal delivery thesis through the skill-native CocoOps thesis workflow. Invoked via $ops dora.
ops-sprint
CocoOps sprint health — computes story velocity, burndown, and completion prediction from git log and sprint window config. Invoked via $ops sprint.
cup-history
Display the last N CocoCupper findings from .cocoplus/grove/cupper-findings.md. Usage: $cup history [n] where n defaults to 5.
fleet-status
Show the current execution state of a CocoFleet run. Displays per-instance status, runtime, and checkpoint results. Usage: $fleet status [fleet-id].