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 commands/iampawan/manifest/ready-checkgit clone --depth 1 https://github.com/iampawan/ManifestWrote 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/commands/iampawan/manifest/ready-check)<a href="https://agentmods.dev/commands/iampawan/manifest/ready-check"><img src="https://agentmods.dev/badge/commands/iampawan/manifest/ready-check.svg" alt="Measured on agentmods" 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.00000 | $0.00995 |
| Opus 5 | $0.00000 | $0.00498 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
ready-check 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ready-check
Airport security for PRDs. Clear this before handing a feature to engineering — no more dev chasing you for basics.
/ready-check <a JIRA / Notion / Doc / Slack / Figma URL, or "a description">
/ready-check # no args → I'll ask you the questions directly
/ready-check panel # (Cowork) open the live sidebar panel
/ready <source> # alias
Invoke the ready-check skill. It reads the source, fills what it can, asks you only what's missing, and gives a clear verdict.
Examples
/ready-check https://your-org.atlassian.net/browse/ENG-1234
/ready-check https://www.figma.com/file/<...> # design-led feature
/ready-check "saved payment cards at checkout, android + ios"
/ready-check "idempotent refund API, payments service" # pure backend — works too
/ready-check # interview me
Works for every PRD — frontend, backend, API, data, infra. A backend PRD answers the same items the backend way (interface/contract spec, response & error codes, endpoints, downstream consumers); there's no "backend → skip it" path, and N/A only clears with a stated reason.
What you get
- Not ready → the exact items to add, in plain words, each with an example. Fix them and re-run.
- Ready → a gate code (
RC-…) and a hand-off block with your design link. Paste it into the ticket or the dev thread. Dev grooms only PRDs with a valid code.
Verifying a hand-off (no panel needed)
/ready-check verify <ticket-or-page-link> # best — nothing to paste
/ready-check verify # then paste the whole block
Give it the link and it fetches the ticket/page and finds the hand-off inside
it — no copying. Pasting works too, but paste the whole block including every
• [id] … line: the gate code is a hash of the answers, so the code on its own
can't be checked against anything (you'll get UNVERIFIABLE).
You get VALID / STALE / INVALID, or UNVERIFIABLE if the block wasn't
produced by the tool (a hand-written block proves nothing). If it carries a freeze
stamp, the PRD and design are re-fetched to confirm nothing changed since sign-off.
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.
- 5d ago First seen · 87 lines · 0 tokens per session scan A f8a5a0f0f3c1
ready-check is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 995 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.