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 manishiitg/coding-agent-loop --skill approved-requirement-to-release-readinessgit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/approved-requirement-to-release-readiness)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/approved-requirement-to-release-readiness"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/approved-requirement-to-release-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/manishiitg/coding-agent-loop/approved-requirement-to-release-readiness"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/approved-requirement-to-release-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.00029 | $0.00576 |
| Opus 5.5 | $0.00012 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
approved-requirement-to-release-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 19d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Approved Requirement to Release Readiness
Outcome
Produce an exact-requirement release readiness decision with named blockers or verified go evidence.
When to use
Use this route when the job crosses the listed owners or access boundaries. A single Crew may do a compatible read-only task. This package is a Builder proposal, not an active automation.
Discovery and user direction
Inspect existing Crews, source access, policy revisions, owner decisions and the exact subject. Ask only for missing facts, then show the proposed route for review.
Required inputs
One accepted requirement, product, build, flag revision and rollout owner; no inferred exposure or adoption. Read current approved requirement, build and flag, independent QA gate, help content and versioned usage rule.
Plan and AgentWorks tools
Create reviewed steps for product-requirements-coordinator (product-requirements-brief/v1) → product-release-coordinator (product-release-readiness/v1). Reuse Crews where compatible; Builder may propose create_crew for a missing role. Validate each typed artifact before the next step and independently re-read current source state. No flag, deployment, help publication or announcement from installation. A go decision is not customer exposure or feature adoption.
Knowledge and persistence
Store tenant, subject, Crew, artifact, source revision, decision, approval and provider receipt IDs. Re-read source truth and deduplicate on repeat; keep prior decisions in the ledger.
Validation and reporting
The contract validator checks exact identity, revisions, time order and route-specific false claims. The first artifact, last artifact and rejected artifact exercise it. The dashboard must separate pending review, owner approval and observed provider action.
Guardrails
A passing QA gate is one input. Product go needs current help, measurement and rollout authority; a no-go names blockers. No flag, deployment, help publication or announcement from installation. A go decision is not customer exposure or feature adoption. Do not count a draft, approval or planned action as a provider outcome.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/invalid-release.json 798 B
- examples/release.json 842 B
- examples/requirements.json 656 B
- playbook.json 4.9 KB
- references/team-and-handoffs.md 1.6 KB
- scripts/category_route_contract.py 7.6 KB runs code
- scripts/test_validate_handoff.py 1.3 KB runs code
- scripts/validate_handoff.py 647 B runs code
- SETUP.json 3.1 KB
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.
- 19d ago First seen · 48 lines · 29 tokens per session scan A fd8de0fa95c6
approved-requirement-to-release-readiness is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 576 once invoked, about $0.0001 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-28.
Other skills, from other repositories
scenario-design
Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…
run-dashboard-e2e-local-changes
Run Playwright E2E (tests/e2e/) against the docker/ all-in-one harness so it reflects LOCAL code changes, not a stale cached image.
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.
goga-accept-usage-review
Validate cell-level usage files against actual implementation during acceptance.
goga-accept-scope
Defines the acceptance scope — the set of cells for a given functionality.
goga-change-test-engineer
Test Coverage Validation and Behavioral Testing.