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/alireza29675/teamctl/claude-mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/claude-md)<a href="https://agentmods.dev/instructions/alireza29675/teamctl/claude-md"><img src="https://agentmods.dev/badge/instructions/alireza29675/teamctl/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.01225 | $0.01225 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
teamctl 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Repo-root governance for human contributors and any Claude Code agents working in this repo. Read this before opening a PR; the rules here apply to every change.
This file is short on purpose. Keep it under roughly 2K tokens and treat it like code — prune what an agent already does without being told, expand only what would otherwise produce a wrong outcome. When you add something here, run the pruning test:
Would removing this instruction cause an agent to make a mistake? If no, delete it.
further reading on writing effective CLAUDE.md files: https://code.claude.com/docs/en/best-practices
What this repo is
teamctl is a multi-crate Rust workspace that ships docker-compose-shaped tooling for persistent agent teams. The crates cover the CLI, the schema / validate / render / supervisor core, the MCP server agents read and write the mailbox through, the Telegram bridge, and the TUI. The repo also carries an Astro Starlight docs site under docs/, cookbook examples under examples/, and a dogfood team config under .team/ — the team that develops teamctl on teamctl, shipped in-tree because it doubles as the showcase.
User-facing intro and install path: see @README.md.
Stack and entry points
Multi-crate Rust workspace, MSRV Rust 1.86 (stable).
crates/teamctl/— the CLI (teamctl init | up | down | reload | status | ...).crates/team-core/— schema, validate, render, supervisor.crates/team-mcp/— MCP server agents talk to.crates/team-bot/— Telegram bridge for user-facing managers.crates/teamctl-ui/— the TUI.
Plus docs/ (Astro Starlight site at teamctl.run), examples/ (cookbook recipes), and .team/ (the dogfood team config; ships because it's the showcase).
Day-to-day commands — use just (defined in justfile), matching CONTRIBUTING.md:
just test # cargo test --workspace
just lint # cargo clippy -- -D warnings + cargo fmt --check
just build # cargo build --release
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 · 75 lines · 1,225 tokens per session scan A c24bf76b67ff
teamctl CLAUDE.md is an instructions file published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 1,225 tokens to every session, about $0.0061 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
takt AGENTS.md
AGENTS.md instructions for nrslib/takt, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
rondoflow CLAUDE.md
Claude Code instructions for rondoflow/rondoflow, covering rondoflow, project overview, tech stack, development and setup.
dos-kernel AGENTS.md
Instructions for anthony-chaudhary/dos-kernel, covering what dos is (the 30-second version), run it yourself first — the 60-second proof, when the user asks you about dos (the consumer moves), build, test, and check your work and the layout in one screen.
PuPu CLAUDE.md
Claude Code instructions for haoxiang-xu/PuPu, covering gitnexus — code intelligence, always do, never do, resources and cli.
dos-kernel GEMINI.md
Instructions for anthony-chaudhary/dos-kernel, covering dos — the part that doesn't believe the agents, the rule, why this matters and setup.
claude-org-ja CLAUDE.md
Claude Code instructions for suisya-systems/claude-org-ja, covering secretary, 事実は出典付きで書く（citation-or-abstain）, 起動時, コミュニケーション and 輸送層（transport）両系 — 既定 renga / opt-in broker.