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/realmpastai-web/claude-design-suiteWrote 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/commands/realmpastai-web/claude-design-suite/plan-sprint)<a href="https://agentmods.dev/commands/realmpastai-web/claude-design-suite/plan-sprint"><img src="https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/plan-sprint/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/commands/realmpastai-web/claude-design-suite/plan-sprint"><img src="https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/plan-sprint.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.00009 | $0.00201 |
| Opus 5 | $0.00005 | $0.00101 |
| Sonnet 5 | $0.00002 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
plan-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 9d 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.
This is a copy
91% identical to plan-sprint — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/plan-sprint
Plan a design sprint.
Steps
- Frame the challenge — Define the sprint question and scope using
design-sprint-planskill. - Assemble the team — Identify roles and participants using
team-workflowskill. - Plan activities — Structure each day's activities using
design-sprint-planskill. - Prepare materials — Define prototyping approach and testing plan.
- Recruit testers — Plan user testing sessions for the final day.
- Set review criteria — Define how sprint outcomes will be evaluated using
design-review-processskill.
Output
Complete sprint plan with challenge statement, team roster, daily schedules, materials list, testing plan, and success criteria.
Consider following up with /handoff after the sprint to document the winning concept.
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.
- 9d ago First seen · 17 lines · 9 tokens per session scan A 464a5f709dd7
plan-sprint is a command published in the GitHub repository realmpastai-web/claude-design-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 201 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to plan-sprint, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.