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/stefanoguerrini/c9s/claude-mdgit clone --depth 1 https://github.com/StefanoGuerrini/c9sWrote 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/stefanoguerrini/c9s/claude-md)<a href="https://agentmods.dev/instructions/stefanoguerrini/c9s/claude-md"><img src="https://agentmods.dev/badge/instructions/stefanoguerrini/c9s/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.02256 | $0.02256 |
| Opus 5 | $0.01128 | $0.01128 |
| Sonnet 5 | $0.00451 | $0.00451 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
c9s 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c9s — Claude Code Dashboard
A simple terminal dashboard for Claude Code. Run c9s, see all your projects and sessions, create new ones, attach to running ones. Zero setup — it reads directly from ~/.claude/.
Inspired by k9s: simple, fast, keyboard-driven.
Vision
- Dashboard-first: Launch c9s → see all your Claude Code projects and sessions across all directories
- Zero setup: Discovers existing sessions from
~/.claude/history.jsonland~/.claude/projects/ - tmux for sessions: Real interactive Claude Code terminals via tmux windows (no in-process terminal emulator)
- Simple: One binary + tmux. No daemon, no plugins, no agent mail. Just a dashboard.
- Future: Extend to other CLI agents (Codex, Gemini) — but Claude Code first.
Data sources (all local, no API)
| What | Where |
|---|---|
| All sessions + projects | ~/.claude/history.jsonl |
| Token usage per session | ~/.claude/projects/<path>/<session>.jsonl → sum message.usage |
| Session name/title | sessions-index.json → customTitle, or history.jsonl → display |
| Session status | JSONL file mtime + ps/lsof process detection |
Testing
Always write tests for every change. No code lands without corresponding test coverage.
- Tests live next to the code they test (
foo_test.goalongsidefoo.go) - Run all tests:
go test ./... -count=1 - Run a specific package:
go test ./internal/claude/ -v - Use
t.TempDir()for any file I/O in tests — never write to real paths - Table-driven tests preferred for functions with multiple input/output cases
- Test both happy paths and edge cases (missing files, empty inputs, etc.)
Architecture
c9s/
├── main.go # Bubbletea TUI + tmux bootstrap + keybindings
├── internal/
│ ├── claude/
│ │ ├── sessions.go # Session discovery, token reading, process detection
│ │ └── sessions_test.go # Tests
│ ├── config/
│ │ ├── config.go # Config loading from ~/.c9s/config.json
│ │ └── config_test.go # Tests
│ ├── git/
│ │ ├── worktree.go # Git worktree discovery + creation
│ │ └── worktree_test.go # Tests
│ └── tmux/
│ ├── tmux.go # tmux CLI wrapper, pane status, status bar
│ ├── tmux_test.go # Tests
│ ├── exec_unix.go # syscall.Exec (Unix)
│ └── exec_windows.go # Stub (Windows)
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 · 183 lines · 2,256 tokens per session scan A ea17fcb0a5dc
c9s CLAUDE.md is an instructions file published in the GitHub repository StefanoGuerrini/c9s (5 stars, last pushed 29d ago), licensed MIT. It adds 2,256 tokens to every session, about $0.0113 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-31.
Other instructions, from other repositories
Vibe-Research AGENTS.md
AGENTS.md instructions for simonlin1212/Vibe-Research, covering vibe-research-agent 金融研究宪法, 0. 三条不可越线, 1. 数据纪律(五问 gate:给出任何数字或结论前逐条自问), 2. 研究哲学(评估框架,不是预测工具) and 3. 估值口径(你只选输入、解释输出;计算交给 calc/).
worldmonitor AGENTS.md
AGENTS.md instructions for koala73/worldmonitor, covering agents.md, own the outcome, start safely, find the code and its checks and critical boundaries.
vizro copilot-instructions.md
Copilot instructions for mckinsey/vizro, covering github copilot instructions for vizro, pull requests from bots and automated tooling and everything else.
openclaw-dashboard CLAUDE.md
Claude Code instructions for mudrii/openclaw-dashboard, covering go development standards, project constraints, internal packages, environment and commands.
metabase copilot-instructions.md
Copilot instructions for metabase/metabase, covering metabase developer assistant instructions, code review standards, security critical issues, performance red flags and code quality essentials.
neko-master copilot-instructions.md
Instructions for foru17/neko-master: All repo guidance lives in AGENTS.md — commands, code conventions, key contracts, and the project map. Follow it.