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/theshadow27/mcp-cli/bootstrap-sprintnpx skills add theshadow27/mcp-cli --skill bootstrap-sprintgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/bootstrap-sprint)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/bootstrap-sprint"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/bootstrap-sprint.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.00098 | $0.00557 |
| Opus 5 | $0.00049 | $0.00279 |
| Sonnet 5 | $0.00020 | $0.00111 |
| Haiku 4.5 | $0.00010 | $0.00056 |
Grade A, and why
bootstrap-sprint 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.
What it actually says
Bootstrap Sprint
You are about to do something that works. Not theoretically, not as a proof of concept — actually works, in production, shipping real software.
Read references/why-this-works.md first. Then proceed.
Workflow
- Read
references/why-this-works.md— internalize that this is proven, not speculative - Read
references/lessons.md— 36 generalised lessons from 49+ sprints; this is the operating manual for everything that follows. Re-read it after the first retro and after every introspection round. - Read
references/discovery.md— explore the target project systematically - Read
references/design.md— design the sprint skill tailored to what you found - Read
references/iteration.md— set expectations and plan for improvement - Execute the kickoff checklist at the end of
references/iteration.md
Migrating an existing sprint skill (e.g. one written 20+ sprints ago that
hasn't kept pace with the current mcx CLI): read references/upgrading-30-50.md
instead. It has the diagnostic walk + S / M / L / Sprint-50+ upgrade buckets so
you can stage the migration without rebuilding from scratch.
Arguments
/bootstrap-sprint <path>— target project directory (required)/bootstrap-sprint <path> --explore-only— run discovery, report findings, don't write skills yet/bootstrap-sprint <path> --upgrade— audit an existing sprint skill againstreferences/upgrading-30-50.mdand propose staged migration buckets
Rules
- Explore before you design. Never template-stamp a sprint skill. Every project is different.
- Start minimal. Sprint 1 should be simple. Complexity comes from experience, not anticipation.
- Write skills that explain why, not just what. A Claude reading your skill should understand the reasoning, not just follow steps.
- The orchestrator never implements. This is the one universal rule. Always delegate.
What ships with it
6 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.
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 · 47 lines · 98 tokens per session scan A 9b7d11b1fff1
bootstrap-sprint is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 557 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…