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 hams-ollo/zen-agent-skills --skill spec-plan-readinessgit clone --depth 1 https://github.com/hams-ollo/zen-agent-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/skills/hams-ollo/zen-agent-skills/spec-plan-readiness)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/spec-plan-readiness"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-plan-readiness/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/hams-ollo/zen-agent-skills/spec-plan-readiness"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/spec-plan-readiness.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.00101 | $0.02174 |
| Opus 5.5 | $0.00040 | $0.00870 |
| Sonnet 5.5 | $0.00020 | $0.00435 |
| Haiku 4.5 | $0.00010 | $0.00217 |
Grade A, and why
spec-plan-readiness 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 1mo 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-plan readiness
Adapted from repoprompt-workflows (Balarama Bosch), MIT.
Uses spec-quality as supporting input.
Intent
Decide whether a readable behavioral spec plus a readable ordered set of task files is implementable before tests, code, or implementation delegation begin.
This skill is a gate. It reports exact blocking gaps and, only when all readiness conditions hold, identifies scenario test layers, task traceability, and the first safe implementation task.
In this kit, the "plan" being gated is not a standalone document: it is a ROADMAP Feature decomposed into ordered .tasks/<id>.md files, per the work-altitude-model section of the repository's AGENTS.md. Wherever this skill says "the plan," it means that ordered task decomposition, read as a set.
Inputs
Required:
- Spec: readable behavioral contract with scenarios, constraints, proposed surface, and open questions.
- Task decomposition: readable ordered set of task files (the roadmap Feature broken into
.tasks/items) with tasks, affected areas, dependencies, validation, test strategy, risks, rollback notes, and task-to-scenario mapping.
Optional:
- Repository context: existing validation commands, test frameworks, surfaces, conventions, and test taxonomy.
If either required input is missing or unreadable, short-circuit: return verdict: blocked, report the missing spec and/or plan gap, leave maps empty, do not evaluate scenarios or tasks, and do not include first_safe_task.
Non-goals
Do not use this skill to:
- write or revise the spec or the task files;
- create tests, production code, refactors, or implementation tasks;
- manage worktrees, progress ledgers, delegated agents, reviews, or closeout validation;
- replace full single-spec review by
spec-quality; - choose product scope beyond naming unresolved decisions, contradictions, and missing coverage.
Workflow
1. Confirm readable inputs
Verify that both the spec and the task decomposition were supplied and can be read.
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.
- 1mo ago Changed · +7 lines b099f27cbf30
- 2mo ago First seen · 188 lines · 101 tokens per session scan A f18ebfd45e4a
spec-plan-readiness is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 101 tokens to every session and 2,174 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-08-31.
Other skills, from other repositories
review
Use when explicitly invoked to review a branch diff (or any diff or files pointed at) with a find-only subagent covering rubric and conventions, change conformance against the AC-N and their runtime-verification evidence, and documentation consistency — one plain-text verdict that reaches lgtm only when no dimension…
implement
Use when explicitly invoked to execute a change's tasks.md from the first unticked step: implement each task, run its validation, commit, then run the quality gate and verify every acceptance criterion by observed behavior. Needs no conversation context — the change folder is the whole input. Trigger on…
archive
Use when explicitly invoked to close out a change whose branch has already merged: confirm the merge from git alone, then move the change folder under changes/archive/ with its ship date. Trigger on '/sw:archive', '$sw:archive', 'archive this change', or a request to close out a merged change.
ship
Use when explicitly invoked to run the whole change ladder without stopping — ticket, plan, implementation, quality gate, runtime verification, review to lgtm — deciding every open question autonomously and recording each decision in proposal.md. Trigger on '/sw:ship', '$sw:ship', or a request to take something from…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…