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/rigos0/superturtle/claude-mdgit clone --depth 1 https://github.com/Rigos0/superturtleWhat 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.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
superturtle 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 3d 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
SuperTurtle User Notes
This file is for humans and turtles working in this repo after installing or upgrading SuperTurtle.
Latest release highlights
- Fixed a Codex stalling issue around pending tool output delivery
- Reduced Telegram push noise: intermediate updates are silent, while the final reply still notifies normally
- Improved process startup and shutdown reliability to reduce duplicate runners and restart cleanup issues
- Added short Telegram startup messages when the turtle process boots
For the full release history, see super_turtle/CHANGELOG.md.
Important migration info
SuperTurtle now keeps its live project state under:
.superturtle/
The active env file is:
.superturtle/.env
The repo-root .env.example is only a reference template. It is not the live runtime env file.
If you are upgrading from an older layout:
- move any active bot env values into
.superturtle/.env - treat
.env.exampleas documentation for available options - use
superturtle initas the canonical setup/update path - do not use the old
setupscript
Common commands
superturtle init
superturtle start
superturtle stop
superturtle status
superturtle doctor
Notes for the turtle
- Prefer
.superturtle/.envfor live config - Prefer repo-root
.env.examplewhen looking up optional env variables - Check
super_turtle/CHANGELOG.mdfirst when behavior changed after an upgrade
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.
- 3d ago First seen · 52 lines · 324 tokens per session scan A c8fcc09d7960
superturtle CLAUDE.md is an instructions file published in the GitHub repository Rigos0/superturtle (123 stars, last pushed 4mo ago), licensed MIT. It adds 324 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
open-code-review AGENTS.md
Instructions for alibaba/open-code-review, covering agent guidelines for open-code-review, project overview, git commit notes, license headers and code style.
eve AGENTS.md
Instructions for vercel/eve, covering agents.md, about eve, repository layout, git workflow and commands.
qm AGENTS.md
AGENTS.md instructions for yc-software/qm, covering qm, working on the code, private forks and durable by default.
senpi AGENTS.md
Instructions for code-yeongyu/senpi, covering senpi repository guide, mandatory execution protocols — non-negotiable, protocol 1 — explicitly requested modifications, protocol 2 — user-requested pr reviews and structure.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
sprawling AGENTS.md
Instructions for 2youg1/sprawling, covering agents.md — how work is done in this repository, the loop, read before you write, one change, five steps and the rules a machine holds.