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/helmi/claude-simone/commitgit clone --depth 1 https://github.com/Helmi/claude-simoneWhat 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.00000 | $0.01484 |
| Opus 5 | $0.00000 | $0.00742 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
commit 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- commit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze changes and create logical git commits with user confirmation
Follow these instructions from top to bottom.
Create a TODO with EXACTLY these 6 items
- Parse arguments and analyze git status
- Review changes and group by logical commits
- Propose commit structure and messages
- Check if user approval is necessary
- Execute approved commits
- Report commit results
1 · Analyze git status and parse arguments
- Run these commands in parallel for maximum efficiency:
git status,git diff --staged,git diff - List all changed files with their folder structure to understand the scope
CRITICAL: Argument Interpretation Rules
Context Provided (when <$ARGUMENTS> contains text):
- If YOLO is part of the <$ARGUMENTS> it is meant to skip user Approval (see Step 4 on your Todo)
- The other text in <$ARGUMENTS> represents a task ID, sprint ID, or other contextual identifier provided by the user
- This is NOT a file path - it's a semantic context for filtering changes
- PRIMARY FOCUS: Only commit files directly related to this context
- SECONDARY CONSIDERATION: After handling the primary context, ask if user wants to commit other unrelated changes
Task ID Pattern (e.g., T01_S02, TX03_S01, T003):
- Sprint Tasks:
T<NN>_S<NN>format (e.g., T01_S02, T03_S02) - Completed Sprint Tasks:
TX<NN>_S<NN>format (e.g., TX01_S02, TX03_S01) - General Tasks:
T<NNN>format (e.g., T001, T002) - Completed General Tasks:
TX<NNN>format (e.g., TX001, TX002) - Search for this task ID in:
.simone/03_SPRINTS/directory (for sprint tasks).simone/04_GENERAL_TASKS/directory (for general tasks)- Task metadata in files (look for
task_id: T01_S02in frontmatter) - Git diff content (to see if code comments or commits reference the task)
- Identify ALL files that were modified as part of this task's implementation
- This includes: source code, tests, configuration, and the task documentation file itself
Sprint ID Pattern (e.g., S01, S02):
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 · 142 lines · 0 tokens per session scan A 79a791b08da0
commit is a command published in the GitHub repository Helmi/claude-simone (558 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,484 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-30.
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.