Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/iampawan/Manifestnpx agentmods add skills/iampawan/manifest/ready-checkWrote 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/iampawan/manifest/ready-check)<a href="https://agentmods.dev/skills/iampawan/manifest/ready-check"><img src="https://agentmods.dev/badge/skills/iampawan/manifest/ready-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00182 | $0.10056 |
| Opus 5 | $0.00091 | $0.05028 |
| Sonnet 5 | $0.00036 | $0.02011 |
| Haiku 4.5 | $0.00018 | $0.01006 |
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 8d 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 — 651 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ready Check (PM-side gate)
The world this is built for: a PM has a PRD and is about to hand it to engineering for grooming and estimation. Today, half-baked PRDs get through, dev chases the PM for basics, and dev eats the delay. Ready Check is the cheap, 2-minute check the PM clears first. Green → a gate code + hand-off; anything missing → the exact gaps, in plain language.
It is deliberately a floor, not the deep judge. The precise, code-grounded
review (regression, security, feasibility, estimate) is Level 2 —
skills/contract-pickup, dev-side. Read reference/READY-CHECK-RUBRIC.md for
the rubric and the PM-vs-dev dividing line.
Works for EVERY PRD — frontend, backend, API, data, infra
This gate is stack-neutral. It is not a UI-only tool, and there is no "this is backend, the tool doesn't apply" escape. Every rubric item has a sensible reading for a pure-backend or API PRD — treat the item, not the label:
| item | frontend reading | backend / API / data reading |
|---|---|---|
design |
Figma / mock link | interface / contract spec — OpenAPI, proto, GraphQL schema, event schema |
states |
empty / loading / done / error copy | response & failure contract — 2xx/4xx/5xx codes, error bodies, ret/idempotency |
flows |
screens touched | endpoints, jobs, queues, consumers touched |
scope |
platforms (iOS/Android/web) | services in scope, and what's explicitly out |
l10n |
copy final & localised | response/payload format finalised (schema version, error codes) |
writer |
writer/creator surface | downstream consumers (services, webhooks, subscribers) |
events |
analytics events | metrics / logs / traces (latency, error-rate, throughput) |
A backend PRD is not cleared by N/A-ing the UI items — it's cleared by answering the backend equivalents above. If a PM says "it won't work, this is backend," that's the signal to run it with these readings, not to skip it.
Runs in both surfaces
This skill is plain markdown + one deterministic script, so it behaves
identically in Claude Code and Cowork. The offline web page
(gate/prd-readiness-gate.html) is the same rubric for PMs with no Claude
open; it mints the same gate-code format, so a code from any surface verifies
in all of them.
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.
- 8d ago First seen · 651 lines · 182 tokens per session scan A 35e380c8b174
ready-check is a skill published in the GitHub repository iampawan/Manifest (5 stars, last pushed 6d ago), licensed MIT. It adds 182 tokens to every session and 10,056 once invoked, about $0.0009 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.