Puppetmaster: Instructions file for Codex

AGENTS.md

Puppetmaster AGENTS.md is an instructions file for Codex, OpenCode from professorpalmer/Puppetmaster. It costs 4,706 tokens per session, scanned A, original, MIT.

Instructions for coding agents working in the Puppetmaster repository, including how to identify worker roles and when a task should use multiple agents.

In plain words
What is it for?
Use them when contributing to Puppetmaster or its related projects, especially when deciding whether to work directly or coordinate a group of agents.
Why use it?
They prevent workers from starting unnecessary agent groups and explain the repository's expected workflow for interactive agents.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions AGENTS.md.

This is professorpalmer/Puppetmaster's own configuration. It tells Codex and OpenCode how to work on Puppetmaster itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Puppetmaster configures →

Reuse

Borrowing it

Nothing to install: this file belongs to professorpalmer/Puppetmaster. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/professorpalmer/Puppetmaster/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/professorpalmer/Puppetmaster

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Puppetmaster AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/professorpalmer/puppetmaster/agents-md/github.svg)](https://agentmods.dev/instructions/professorpalmer/puppetmaster/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/professorpalmer/puppetmaster/agents-md"><img src="https://agentmods.dev/badge/instructions/professorpalmer/puppetmaster/agents-md/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.

agentmods 80×15 button for Puppetmaster AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/professorpalmer/puppetmaster/agents-md"><img src="https://agentmods.dev/badge/instructions/professorpalmer/puppetmaster/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,706 This file is loaded in full into every session.
When invoked 4,706 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04706 $0.04706
Opus 5.5 $0.01882 $0.01882
Sonnet 5.5 $0.00941 $0.00941
Haiku 4.5 $0.00471 $0.00471

Measured 20d ago against content hash b26e6b2c2bb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Puppetmaster AGENTS.md 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 20d 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.

AGENTS.md · 213 lines

How it starts

The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Repo-level guidance for AI coding agents (Cursor, Claude Code, Codex, etc.) working in this repository. Cursor users see the same directive via .cursor/rules/puppetmaster-workflow.mdc.

First: are you a Puppetmaster worker?

If your prompt was issued by Puppetmaster, everything below about starting a swarm does not apply to you. You are the swarm. Do the analysis or the edit yourself, directly, and return the artifacts your prompt asks for.

You are a Puppetmaster worker if PUPPETMASTER_WORKER=1, or your prompt contains any of:

  • a Puppetmaster artifact contract: / Return only Puppetmaster artifact JSON block,
  • a Role: <role> + Goal: <goal> header,
  • an instruction to finish by calling submit_findings or submit_report.

Workers are spawned by puppetmaster.worker_runtime as plain agent CLIs. They have no Puppetmaster MCP tools, so "start a swarm before exploring" is an instruction they cannot follow — following it costs a full context load and returns a request for clarification instead of findings. Nested job starts (python -m puppetmaster swarm, MCP start verbs) are refused while PUPPETMASTER_WORKER=1. Override: PUPPETMASTER_ALLOW_NESTED=1. Roll your own grep/read loop; that is your job.

The rest of this file addresses an interactive agent working with the user, which has the MCP tools available. Pi is in that class: a TUI/pilot via the bundled @puppetmaster/pi-pilot package (puppetmaster install-pi-mcp / setup --platforms pi). OMP / oh-my-pi is the same class via native MCP (puppetmaster install-omp-mcp / setup --platforms omp or ohmypi; writes ~/.omp/agent/mcp.json). Use start_implement / start_agentic / start_prewalk, consume artifacts, nuke the job. Do not lease pi or omp as a worker.

Puppetmaster is the fan-out runtime, not the default for everything

When this repo is open, and you are not a Puppetmaster worker (see above), do the work yourself unless parallel workers clearly finish sooner or better. When work does fan out, Puppetmaster is the path, not ad-hoc subagents.

Read the full file on GitHub · 213 lines

Changes

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.

  1. 20d ago Changed · +5 lines · +36 tokens per session b26e6b2c2bb2
  2. 22d ago Changed · +1 lines · +63 tokens per session 8013c55ab69e
  3. 1mo ago Changed · +31 tokens per session f1079420fcc3
  4. 1mo ago Changed · +3 lines · +56 tokens per session e5abea28cd89
  5. 1mo ago First seen · 204 lines · 4,520 tokens per session scan A 3ff5bb80bc8e

Subscribe to this mod's changes

Puppetmaster AGENTS.md is an instructions file published in the GitHub repository professorpalmer/Puppetmaster (471 stars, last pushed 3d ago), licensed MIT. It adds 4,706 tokens to every session, about $0.0188 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens