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/felipecabargas/gambit/fr-to-readygit clone --depth 1 https://github.com/felipecabargas/gambitWrote 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/agents/felipecabargas/gambit/fr-to-ready)<a href="https://agentmods.dev/agents/felipecabargas/gambit/fr-to-ready"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/fr-to-ready.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.00110 | $0.01094 |
| Opus 5 | $0.00055 | $0.00547 |
| Sonnet 5 | $0.00022 | $0.00219 |
| Haiku 4.5 | $0.00011 | $0.00109 |
Grade A, and why
fr-to-ready 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FR to Ready Agent
Overview
This agent is a three-skill chain that closes the gap between a raw feature idea and a dev-ready state. It runs write-feature-request, verify-acceptance-criteria, and write-technical-brief in sequence, producing a complete handoff package that engineering can act on without needing to chase down missing context.
The three components and what each produces:
- write-feature-request — guides you through a structured conversation to produce a complete FR with problem statement, user stories, and acceptance criteria
- verify-acceptance-criteria — evaluates every AC against five quality dimensions and rewrites failing criteria before they reach engineering
- write-technical-brief — translates the verified FR into an engineering-facing document covering architecture considerations, implementation approach, and open questions
Chain
write-feature-request → verify-acceptance-criteria → write-technical-brief
How It Runs
Step 1 — Write the Feature Request
Run write-feature-request in full guided conversation mode. The skill asks clarifying questions, surfaces edge cases, and produces a complete FR with a problem statement, user stories, and a set of acceptance criteria.
Save output in the standard write-feature-request format.
Pause here: present the completed FR to the user for review. Ask: "Here is the Feature Request. Does this capture what you intend to build? Confirm to continue with AC verification, or provide corrections first."
Do not proceed to Step 2 until the user confirms.
Step 2 — Verify and Rewrite Acceptance Criteria
Pass all ACs from the FR into verify-acceptance-criteria. The skill evaluates each AC against five quality dimensions: testability, clarity, completeness, scope, and independence.
For any AC that fails verification, automatically produce a rewritten version. Present a diff to the user showing original and rewritten ACs side by side.
Ask: "Here are the AC rewrites. Do you approve these changes? You can accept all, reject individual rewrites, or provide your own edits."
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 · 95 lines · 110 tokens per session scan A caa5ded726f8
fr-to-ready is an agent published in the GitHub repository felipecabargas/gambit (2 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 1,094 once invoked, about $0.0006 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 agents, from other repositories
antigravity-delegate
Use this subagent PROACTIVELY — don't wait for the user to ask for delegation — whenever a task contains a well-scoped, ABOVE-break-even unit of work for the Antigravity CLI (agy / Gemini): bulk scaffolding, exhaustive test generation, migrations, long-context reads that distill to a digest, or fan-out web / Vertex AI…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
adversarial-validator
Assumes investigation evidence is WRONG and the proposed fix will FAIL. Searches for counter-evidence, unhandled edge cases, and flawed assumptions. Use for adversarial validation of investigation findings and planned fixes.
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.