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 commands/codeverbojan/claude-code-kickstart/resetgit clone --depth 1 https://github.com/codeverbojan/claude-code-kickstartWhat 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.00018 | $0.00257 |
| Opus 5 | $0.00009 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
reset 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 yesterday.
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
Reset Session
Three phases, in order. Don't skip.
Phase 1: Wrap up
Run the full /wrap-up flow: verify, rewrite primer.md, update
decisions.md/gotchas.md/metrics.jsonl. Don't report to the user yet.
Phase 2: Clear context
Tell the user: "Session state saved. Clearing context and restarting fresh."
Then run /clear.
Phase 3: Deep onboard
The SessionStart hook auto-loads primer.md (and any non-stub
gotchas/patterns/decisions) on session resume. Then run /onboard deep to
get the full project explore + status report.
If the user provided a task with /reset, pass it through to /onboard deep
so the onboard focuses on that task.
When to use
- Context is degraded (forgetting files, editing stale content, hallucinating).
- Switching to a completely different area of the codebase.
- After a long session (20+ messages).
- After a large merge or rebase.
$ARGUMENTS
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.
- yesterday First seen · 33 lines · 18 tokens per session scan A a08a31f8a8ed
reset is a command published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 257 once invoked, about $0.0001 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 commands, from other repositories
stats
Show token-saver compression statistics and savings.
implement
Execute implementation by processing atomic task files one at a time with Context Pinning (Atomic Traceability Model).
cleanup
Detect and remove orphaned code, unused components, dead routes, and stale database artifacts.
specify
Create or update the feature specification from a natural language feature description.
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
amby.converge
Check the codebase against spec, plan, and tasks after implementing; append gap tasks, never edit code.