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 instructions/helmi/claude-simone/claude-mdgit 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/instructions/helmi/claude-simone/claude-md)<a href="https://agentmods.dev/instructions/helmi/claude-simone/claude-md"><img src="https://agentmods.dev/badge/instructions/helmi/claude-simone/claude-md.svg" alt="Measured on agentmods" 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.00319 | $0.00319 |
| Opus 5 | $0.00160 | $0.00160 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
claude-simone CLAUDE.md 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 6d 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
CLAUDE Instructions - Simone Repository
IMPORTANT: This is a meta-repository situation. Be aware that this repo is used to develop a system called "Claude Simone" which is an addon to Claude Code to manage Tasks and Work. At the same time this repository itself uses Simone to organize its own work (currently the mcp-server based version).
Activity Logging
You have access to the log_activity tool. Use it to record your activities after every activity that is relevant for the project. This helps track development progress and understand what has been done.
Repository Structure
-
/legacy- The stable, production-ready Simone system- Directory-based command system
- Fully functional and documented
- Use this for actual project management
-
/hello-simone- NPM installer for legacy Simone- Installs the legacy system
- Run with
npx hello-simone
-
/mcp-server- New MCP implementation (early development)- Model Context Protocol based
- Not ready for use
- Active development
⚠ None of these directories should have dependencies outside. If you spot something, report it to the user.
- ADDITIONALLY the meta part: ./simone contains the Framework files for this repo.
Important Notes
- The legacy system is fully functional - use it for actual project management
- The MCP server is in early development and used for this project (with a dev version directly linked)
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.
- 6d ago First seen · 33 lines · 319 tokens per session scan A a701ea18a6d3
claude-simone CLAUDE.md is an instructions file published in the GitHub repository Helmi/claude-simone (558 stars, last pushed 1y ago), licensed MIT. It adds 319 tokens to every session, about $0.0016 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.