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/Helmi/claude-simoneWrote 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/helmi/claude-simone/initialize)<a href="https://agentmods.dev/commands/helmi/claude-simone/initialize"><img src="https://agentmods.dev/badge/commands/helmi/claude-simone/initialize/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/helmi/claude-simone/initialize"><img src="https://agentmods.dev/badge/commands/helmi/claude-simone/initialize.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.00821 |
| Opus 5.5 | $0.00000 | $0.00328 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
initialize 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 1mo 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:
- initialize — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Simone Framework
Initialize the Simone project management framework through an adaptive, interactive process.
Create a TODO with EXACTLY these items
- Scan and analyze the project
- Interactive confirmation with user
- Check for existing Simone documents
- Guide document creation process
- Create first milestone for Simone
- Generate project manifest
- Provide next steps
DETAILS on every TODO item
1. Scan and analyze the project
Detect project characteristics:
- Check for package.json, requirements.txt, composer.json, etc.
- Identify project type (Node.js, Python, PHP, etc.)
- Scan overall project structure
- Check if this is a new or existing project
- Look for existing documentation (README, docs/, etc.)
Keep findings brief - Just identify the essentials
2. Interactive confirmation with user
Present findings conversationally:
I found this to be a [project type] project named [detected name].
Is this correct? Should I proceed with Simone setup?
Get user confirmation before continuing
3. Check for existing Simone documents
Scan .simone/ directory for:
- Any documents in 01_PROJECT_DOCS/
- Any milestones in 02_REQUIREMENTS/
- Any existing sprints or tasks
- Current manifest status
Interactive decision:
- If documents found: "I found existing documents: [list]. Should we work with these or extend them?"
- If no documents: "No Simone documents found yet. Do you have any existing project documentation you'd like to copy in before we continue?"
Allow user to:
- Use existing documents
- Add new documents
- Start fresh
- Cancel to add documents manually first
4. Guide document creation process
Based on user's choice:
If starting fresh or extending:
- Perform deep analysis of the codebase
- Identify key components and architecture patterns
- Create draft ARCHITECTURE.md based on analysis
- Use Q&A style to refine and complete:
- "What's the main purpose of this project?"
- "What are the key technical decisions?"
- "Any important constraints or requirements?"
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.
- 1mo ago First seen · 135 lines · 0 tokens per session scan A 68a43b6867ea
initialize is a command published in the GitHub repository Helmi/claude-simone (559 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 821 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.