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/moneytosms/claude-startWrote 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/moneytosms/claude-start/plan)<a href="https://agentmods.dev/commands/moneytosms/claude-start/plan"><img src="https://agentmods.dev/badge/commands/moneytosms/claude-start/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/commands/moneytosms/claude-start/plan"><img src="https://agentmods.dev/badge/commands/moneytosms/claude-start/plan.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.00000 | $0.00286 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
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 2mo 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
/plan
Scaffold a structured plan file for a task or feature.
Steps
- Ask (or infer from context) the plan name — short, kebab-case
- Get today's date:
date +%Y-%m-%d - Create
.claude/plans/YYYY-MM-DD-<name>.mdwith the template below - Fill in Goal, Constraints, and Acceptance Criteria from the context given
- Leave Unresolved Questions blank for the human to answer
- Report the file path created
Template
# Plan: <name>
Date: YYYY-MM-DD
## Goal
<One paragraph: what this plan accomplishes and why.>
## Constraints
- <hard limits: time, tech choices, must-not-touch areas>
## Acceptance Criteria
- [ ] <specific, testable condition>
- [ ] <specific, testable condition>
## Unresolved Questions
- [ ] <question that must be answered before or during execution>
## Tasks
<!-- Populated as work begins -->
## Progress
<!-- DocWriter appends here at session end -->
Rules
- Do not start implementing. Plan only.
- If you lack enough context to fill Goal/Constraints/AC, run
/grill-mefirst. - Plans live in
.claude/plans/— never in the project source tree.
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.
- 2mo ago First seen · 45 lines · 0 tokens per session scan A f9c659336050
plan is a command published in the GitHub repository moneytosms/claude-start (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 tokens. 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 commands, from other repositories
add-feature
Add a new feature to this Quiver app: $ARGUMENTS.
add-test
Command "add-test" from go4cas/quiver, covering step 1 — determine test type, step 2 — write unit tests (vitest), step 3 — write e2e tests (playwright) and step 4 — run and fix.
add-composable
Create a new Quiver composable named: $ARGUMENTS.
add-layout
Create a new Quiver layout named: $ARGUMENTS.
add-page
Create a new Quiver page for the route path: $ARGUMENTS.
add-theme
Add a new visual theme to this Quiver app: $ARGUMENTS.