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.
git clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/agents/richfrem/agent-plugins-skills/planning-doc-agent)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/planning-doc-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/planning-doc-agent/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/agents/richfrem/agent-plugins-skills/planning-doc-agent"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/planning-doc-agent.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.00099 | $0.01960 |
| Opus 5.5 | $0.00040 | $0.00784 |
| Sonnet 5.5 | $0.00020 | $0.00392 |
| Haiku 4.5 | $0.00010 | $0.00196 |
Grade A, and why
planning-doc-agent 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 10d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ OPTIONAL — This agent is only useful when an execution harness plugin is present and the quantum double diamond framework is in use. If you are running exploration as a standalone discovery tool (no execution harness, no double diamond), skip this agent entirely — your workflow ends at
exploration/handoffs/handoff-package.md.
Role in the Quantum Double Diamond Framework
The exploration cycle is Diamond 1 (Discover → Define). The Spec-Kitty engineering cycle is Diamond 2 (Develop → Deliver). This agent bridges the two — but the bridge is optional and must be explicitly enabled.
The relationship is bidirectional:
- Exploration → Spec-Kitty: pre-draft artifacts from the handoff package to smooth the transition into the engineering cycle
- Spec-Kitty → Exploration: when the engineering cycle uncovers unresolved ambiguity, scope and trigger a new exploration cycle (cycling back to Diamond 1)
Multiple exploration cycles may be spawned during a single engineering cycle, including:
- During spec authoring — unclear requirements or missing business rules
- During work package planning — unclear scope, constraints, or dependencies
- During implementation — unknown unknowns surface that require discovery before proceeding
In all re-entry cases, exploration is not a failure mode — it is a designed feedback loop.
Invocation Modes
Mode: spec-draft
Pre-drafts spec.md from the handoff package. Output goes to staging — not directly into kitty-specs/.
pythonscripts/dispatch.py \
--agent .agents/agents/exploration-cycle-plugin-planning-doc-agent.md \
--context exploration/handoffs/handoff-package.md \
--instruction "Mode: spec-draft. Pre-draft a spec.md from this exploration handoff. Follow Spec-Kitty spec format. Mark any gap with [NEEDS HUMAN INPUT]. Output to staging only." \
--output exploration/planning-drafts/spec-draft.md
Mode: plan-draft
Pre-drafts plan.md with high-level phases and work package hints from the handoff.
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.
- 10d ago Changed · +1 lines 92e8cb322ddd
- 1mo ago First seen · 171 lines · 99 tokens per session scan A e974e0140dcd
planning-doc-agent is an agent published in the GitHub repository richfrem/agent-plugins-skills (7 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,960 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
ap-run-coordinator
Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.
ap-work-group-manager
Divide one accepted work group only when at least two useful workers can have non-overlapping ownership.
factory-ci-doctor
Diagnostician for one red GitHub Actions run. Spawn it after a run has failed — never to wait for one (gh run watch --exit-status does that for free) — with the repo and run ID or PR number, so the failed-job logs never enter the caller's context. It returns the culprit job/step, the offending log lines, and a TICKET…
financial-manager
Budget planning, cost estimation, SOW creation, and financial tracking for automotive software projects.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.