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 skills/felipecabargas/gambit/write-roadmapnpx skills add felipecabargas/gambit --skill write-roadmapgit clone --depth 1 https://github.com/felipecabargas/gambitWhat 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 | $0.00110 | $0.02575 |
| Opus 5 | $0.00055 | $0.01288 |
| Sonnet 5 | $0.00022 | $0.00515 |
| Haiku 4.5 | $0.00011 | $0.00258 |
Grade A, and why
write-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 2d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roadmap Writer
When to Use
Use this skill when you need to translate strategy and OKRs into a clear, communicable picture of what the team is working on and why. It adds the most value when:
- Starting a planning cycle — turn a freshly written strategy or set of OKRs into a roadmap the team and stakeholders can reason about. Use immediately after
write-okrsto close the loop from strategy through measurement to planned work. - Communicating priorities to stakeholders — when leadership, sales, or external partners ask "what are you building and when?", a horizon-based roadmap gives an honest, durable answer without over-committing to specific dates.
- Aligning engineering on what's coming — engineers need enough forward visibility to make good technical decisions (avoiding premature optimisation, planning for capacity, flagging risks early). A Now/Next/Later roadmap provides that signal without locking in requirements before they're understood.
Input Format
The skill scans the current project directory for STRATEGY.md and any OKR documents automatically. If found, it reads strategy pillars and Key Results to derive roadmap themes. You can also provide:
Path to strategy and OKR documents:
Strategy: ./STRATEGY.md
OKRs: ./OKRs-Q2-2026.md
Pasted priorities or strategic pillars:
Pillar 1: Improve activation for self-serve sign-ups
Pillar 2: Expand into the mid-market segment
Pillar 3: Lay the compliance foundation for enterprise deals
A description of current priorities:
We're focused on activation this quarter, with mid-market expansion as our next
big push. Compliance work (SOC 2, SSO) is important but 2+ quarters out.
Optionally, backlog items to place on the roadmap:
- Redesigned onboarding flow
- API rate limiting
- SSO integration
- Mobile app (iOS)
- Advanced analytics dashboard
If backlog items are provided, the skill assigns each item to a horizon and a theme rather than listing them as raw tickets. The roadmap stays theme-based even when the input is feature-level.
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.
- 2d ago First seen · 227 lines · 110 tokens per session scan A ca4494df13dc
write-roadmap is a skill published in the GitHub repository felipecabargas/gambit (2 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 2,575 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 skills, from other repositories
antigravity
Run the Antigravity CLI (Gemini) as a collaborating AI inside Claude Code, with intelligent model routing across the software development lifecycle. Claude is the conductor/orchestrator — requirements, architecture, the hard 20%, verification, and review — and routes deterministic, high-volume work (scaffolding…
migrate-to-antigravity
Move an existing Claude Code setup onto the Antigravity CLI (agy) — user skills, CLAUDE.md, auto-memory, MCP servers, installed plugins, permissions and trusted workspaces. Use when the user says "migrate to Antigravity", "move my Claude Code config to agy", "bring my skills/memory/MCP over", "set up agy like my…
vr-planner
Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML…
openqa-log-analyzer
A specialized skill for analyzing openQA logs — triage failures, measure command timing, detect infrastructure lag, extract command output, and compare runs across multiple log files.
local-lint-test
Recommends the fastest local commands to validate edited OSADO code before pushing. Activate when the user asks "how do I check my code", "what should I run locally", "lint my changes", "does this compile", "run perltidy", "run perlcritic", "run a unit test", "check formatting", or after editing files to verify…
test-catalog
Add or audit a Perldoc documentation header on an OSADO test module following the test catalog standard. Use when a user asks to "add header", "document", or "add catalog header" to a Perl test module.