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 faizkhairi/claude-code-blueprint --skill sprint-plangit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/sprint-plan)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/sprint-plan"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/sprint-plan/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/faizkhairi/claude-code-blueprint/sprint-plan"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/sprint-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00107 | $0.00377 |
| Opus 5 | $0.00053 | $0.00188 |
| Sonnet 5 | $0.00021 | $0.00075 |
| Haiku 4.5 | $0.00011 | $0.00038 |
Grade A, and why
sprint-plan 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 10d 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
Create a sprint plan for: $ARGUMENTS
- Analyze the requirement: Understand scope, constraints, dependencies
- Check existing code: Search codebase for related implementations that can be reused
- Break into tasks:
- Each task should be independently deliverable
- Include file paths that will be modified or created
- Estimate size: S (< 1hr), M (1-4hr), L (4-8hr), XL (> 1 day)
- Sequence tasks: Identify dependencies, mark blocking tasks, find parallelizable work
- Identify risks: What could go wrong? What needs clarification?
- Output format:
Sprint Plan: [Feature Name]
Tasks
| # | Task | Size | Depends On | Files |
|---|---|---|---|---|
| 1 | ... | S | - | path/to/file |
Risks
- [Risk description and mitigation]
Definition of Done
- All tasks completed
- Tests written and passing
- Code reviewed
- Documentation updated
- No security vulnerabilities introduced
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.
- 10d ago First seen · 36 lines · 107 tokens per session scan A 13c8113697ba
sprint-plan is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 29d ago), licensed MIT. It adds 107 tokens to every session and 377 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-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.