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.
git 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/strategy-to-roadmap)<a href="https://agentmods.dev/agents/felipecabargas/gambit/strategy-to-roadmap"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/strategy-to-roadmap/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/agents/felipecabargas/gambit/strategy-to-roadmap"><img src="https://agentmods.dev/badge/agents/felipecabargas/gambit/strategy-to-roadmap.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.00113 | $0.01244 |
| Opus 5.5 | $0.00045 | $0.00498 |
| Sonnet 5.5 | $0.00023 | $0.00249 |
| Haiku 4.5 | $0.00011 | $0.00124 |
Grade A, and why
strategy-to-roadmap 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy to Roadmap Agent
Overview
This agent is a three-skill chain that produces the complete planning artefact set — strategy, OKRs, and roadmap — built and aligned in a single session. It runs write-product-strategy, write-okrs, and write-roadmap in sequence, with each document grounded in the one before it.
The three components and what each produces:
- write-product-strategy — guides you through a structured session to produce a product strategy document covering vision, strategic pillars, target customers, and success criteria; saved as
STRATEGY.md - write-okrs — reads the strategy pillars and success criteria and derives a set of Objectives and Key Results for the planning period; challenges vague KRs and distinguishes outputs from outcomes; saved as
OKRs-[period].md - write-roadmap — takes the strategy and OKRs as input and produces a horizon-based roadmap that shows how near-term work maps to strategic bets; saved as
ROADMAP.md
Chain
write-product-strategy → write-okrs → write-roadmap
How It Runs
Step 1 — Write the Product Strategy
Run write-product-strategy in full guided session mode. The skill asks questions about vision, target customers, strategic bets, competitive context, and success criteria, then produces a complete strategy document.
Save output as STRATEGY.md.
Pause here: present the completed strategy to the user for review. Ask: "Here is the product strategy. Does this accurately reflect your intent and priorities? Confirm to continue with OKR writing, or provide corrections first."
Do not proceed to Step 2 until the user confirms.
Step 2 — Write OKRs
Feed the strategy pillars and success criteria from STRATEGY.md into write-okrs. The skill derives 2–4 Objectives, one per strategic pillar, and 2–4 Key Results per Objective. It challenges vague KRs and rewrites any output-focused KRs as outcome-focused ones.
Save output as OKRs-[period].md, where [period] is the planning period derived from the strategy document.
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 First seen · 95 lines · 113 tokens per session scan A e9ba78aea437
strategy-to-roadmap is an agent published in the GitHub repository felipecabargas/gambit (2 stars, last pushed 4mo ago), licensed MIT. It adds 113 tokens to every session and 1,244 once invoked, about $0.0005 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 agents, from other repositories
support-assistant
Use when: handling helpdesk tickets, technical support, or customer service conversations. Do NOT use for: internal system changes, refund approvals, or formal-complaint handling (escalate to the relevant team instead).
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.
technical-business-analyst
Technical business analysis specialist. Invoke for implementation plans, user stories, requirements documents, functional specifications, scope definition, gap analysis, ADRs, RAID logs, and task decomposition. Returns structured documents with exact detail, no placeholders.
pmo
Enterprise PMO. Owns plugins/pmo/ and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.
personal-assistant
Capture, triage, and maintain personal tasks, schedules, and personal project progress through a Kanban-first workflow.
prd-planner
Clarify product requirements, scope, acceptance criteria, and product decisions.