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/versoxbt/claude-initial-setup/plangit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00010 | $0.00488 |
| Opus 5 | $0.00005 | $0.00244 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Plan
Analyze requirements and produce a structured, phased implementation plan with dependencies and risks.
Steps
-
Clarify requirements:
- Identify the feature or change to implement.
- List the functional requirements (what it must do).
- List the non-functional requirements (performance, security, scalability).
- Identify any ambiguities and resolve them before planning.
-
Analyze the existing codebase:
- Identify files and modules that will be affected.
- Map out dependencies between affected modules.
- Note existing patterns and conventions to follow.
- Identify any technical debt that may complicate implementation.
-
Break down into phases:
- Phase 1: Foundation — data models, schemas, types, and interfaces.
- Phase 2: Core logic — business rules, services, and utilities.
- Phase 3: Integration — API endpoints, UI components, and wiring.
- Phase 4: Testing — unit, integration, and E2E tests.
- Phase 5: Refinement — error handling, validation, edge cases.
-
For each phase, list specific tasks:
- File path and what will be created or modified.
- Function or component name and its responsibility.
- Dependencies on other tasks within or across phases.
- Estimated complexity (low, medium, high).
-
Identify risks and mitigations:
- Technical risks: unfamiliar APIs, complex integrations, performance concerns.
- Dependency risks: external services, third-party libraries, team coordination.
- For each risk, propose a mitigation strategy or fallback plan.
-
Define the testing strategy:
- What unit tests are needed and for which modules.
- What integration tests cover the feature end-to-end.
- What E2E tests validate the user flow.
- Target coverage: 80% or higher.
-
Review the plan for completeness:
- Verify all requirements are addressed.
- Verify dependencies are correctly ordered.
- Check that no steps are missing or redundant.
If Requirements Are Unclear
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.
- 2d ago First seen · 61 lines · 10 tokens per session scan A a494ec4eb729
plan is a command published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 488 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.