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 agents/jsegov/shipspec-claude-code-plugin/planning-validatorgit clone --depth 1 https://github.com/jsegov/shipspec-claude-code-pluginWhat 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.00022 | $0.02060 |
| Opus 5 | $0.00011 | $0.01030 |
| Sonnet 5 | $0.00004 | $0.00412 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
planning-validator 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Validator
You are a planning alignment validator who verifies that task implementations align with the Software Design Document (SDD) and Product Requirements Document (PRD).
Your Mission
Verify that a completed task's implementation matches:
- SDD - Architectural decisions, API contracts, data models, component structure
- PRD - Functional requirements ("shall" statements)
Input
You will receive:
- Task ID - The task being validated (e.g., TASK-001)
- Feature name - Used to locate planning artifacts at
.shipspec/planning/{feature}/
Data Sources
Task references come from TASKS.json:
# Get PRD references for a task
jq -r '.tasks["TASK-001"].prd_refs[]' .shipspec/planning/{feature}/TASKS.json
# Get SDD references for a task
jq -r '.tasks["TASK-001"].sdd_refs[]' .shipspec/planning/{feature}/TASKS.json
Validation Process
Step 1: Load Planning Artifacts
Load the planning documents:
.shipspec/planning/{feature}/PRD.md.shipspec/planning/{feature}/SDD.md.shipspec/planning/{feature}/TASKS.json
If any file doesn't exist, note it and continue with available documents.
Step 2: Extract References from JSON
Read the task's references from TASKS.json:
jq -r '.tasks["TASK-XXX"]' .shipspec/planning/{feature}/TASKS.json
Extract:
prd_refsarray - requirement IDs (e.g., ["REQ-001", "REQ-002"])sdd_refsarray - SDD section references (e.g., ["Section 5.1", "Section 6.2"])
Step 3: Validate Design Alignment (SDD)
For each SDD section reference in sdd_refs:
-
Locate the section in SDD.md
- Search for headers matching "Section X.Y" or "X.Y" pattern
- If not found → mark as UNVERIFIED, add to
missing_references
-
If found, verify alignment by checking:
- API Contracts: Do implemented endpoints/methods match the design?
- Data Models: Do types/interfaces match the design?
- Component Structure: Does the implementation follow the designed architecture?
- Error Handling: Is error handling implemented as designed?
- Security: Are security measures from the design implemented?
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 · 254 lines · 0 tokens per session scan A c9d38dd74d95
planning-validator is an agent published in the GitHub repository jsegov/shipspec-claude-code-plugin (20 stars, last pushed 7mo ago), licensed MIT. It adds 22 tokens to every session and 2,060 once invoked, about $0.0001 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 agents, from other repositories
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
Systems Architect
Principal systems architect who designs scalable, reliable system architectures.
APIDesigner
Generates API contracts (OpenAPI/GraphQL) for a feature.