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 agentmods add rules/professorpalmer/puppetmaster/puppetmaster-workflowgit clone --depth 1 https://github.com/professorpalmer/PuppetmasterWhat 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 | $0.02401 | $0.02401 |
| Opus 5 | $0.01201 | $0.01201 |
| Sonnet 5 | $0.00480 | $0.00480 |
| Haiku 4.5 | $0.00240 | $0.00240 |
Grade A, and why
puppetmaster-workflow 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 2d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First: are you a Puppetmaster worker?
If your prompt was issued by Puppetmaster, none of the "start a swarm" guidance below applies to you. You are the swarm. Do the analysis or the edit yourself and return the artifacts your prompt asks for.
You are a Puppetmaster worker if your prompt contains a Puppetmaster artifact contract: block, a Role: <role> + Goal: <goal> header, or an instruction to
finish by calling submit_findings / submit_report. Workers run as plain
agent CLIs with no Puppetmaster MCP tools, so delegating is impossible;
attempting it burns the context window and returns a clarifying question instead
of findings. Roll your own grep/read loop — that is your job.
The rest of this file addresses an interactive agent working with the user, which does have the MCP tools.
Puppetmaster is the Default Subagent Runtime
When this repo is open — and you are not a Puppetmaster worker (see above) — Puppetmaster's MCP tools are the primary path for fanning out work. Do not roll your own grep/read exploration loops or invoke ad-hoc subagents when a Puppetmaster swarm is available.
When you MUST start a Puppetmaster swarm (no permission needed)
For any user request that involves more than a single trivial change, start a Puppetmaster swarm before spending tokens on your own exploration:
- Broad repo investigation, audit, or risk analysis ("review this", "find issues", "what could break").
- Multi-file refactors, migrations, or cross-cutting cleanups.
- Debugging that requires tracing call graphs, data flow, or test coverage across multiple files.
- Planning the next implementation slice when scope or risks are unclear.
- Comparing approaches, surfacing trade-offs, or producing decision artifacts.
The default routing is:
- Call
puppetmaster_start_cursor_swarm(read-only multi-role analysis) — this is the daily-driver entry point. - For implementation that needs durable patches, logs, and dirty-tree guards, use
puppetmaster_start_implementin a clean worktree — it routes to whatever platform the lock enables (cursor preferred, then claude-code).puppetmaster_start_cursor_implement/puppetmaster_start_claude_implementforce a specific platform. - For a single fast review or plan pass,
puppetmaster_start_cursor_review/puppetmaster_start_cursor_planare acceptable lighter alternatives.
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.
- 2d ago First seen · 133 lines · 2,401 tokens per session scan A 1ac4d852116f
puppetmaster-workflow is a cursor rule published in the GitHub repository professorpalmer/Puppetmaster (349 stars, last pushed 3d ago), licensed MIT. It adds 2,401 tokens to every session, about $0.0120 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 cursor rules, from other repositories
x402-coding
@dexterai/x402 SDK conventions and hosted-only OpenDexter tool usage.
pn-build-gate
For build/design/scaffold requests, load pn-build or pn-design; discovery and skeptic mandatory. For fix/tweak, use skills directly.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).
pn-babylon
Babylon.js scene structure, disposal, and performance. Use when editing Babylon.js or 3D scene code.
pn-communication-contract
Concise agent chat — lead with the answer, ban hedging/slop, scope lock, response aliases (scr/eli/foc/ref/scp). Use when responses are verbose, user asks to compress, or those aliases appear.
pn-astro
Astro conventions: islands, SSG, client directives. Use when editing .astro files. For React components used as Astro islands, pn-react also applies.