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/atomchung/ccstory/agents-mdgit clone --depth 1 https://github.com/atomchung/ccstoryWrote 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/atomchung/ccstory/agents-md)<a href="https://agentmods.dev/instructions/atomchung/ccstory/agents-md"><img src="https://agentmods.dev/badge/instructions/atomchung/ccstory/agents-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 | $0.00896 | $0.00896 |
| Opus 5 | $0.00448 | $0.00448 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
ccstory AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ccstory agent guide
This is the canonical repository guide for coding agents. Codex and
Antigravity read it directly; Claude Code reads it through the thin
CLAUDE.md import. Keep shared rules here rather than copying them into
tool-specific files.
Instruction layers
- Neutral product facts belong in the code,
README.md, architecture docs, or ADRs. Do not turn this file into a second product encyclopedia. - Shared expectations for how any coding agent should work belong here.
- Claude Code-only deltas belong below the
@AGENTS.mdimport inCLAUDE.md. - Antigravity-only deltas belong in
GEMINI.mdor.agents/rules/when a real Antigravity-specific need appears. - Codex-only settings belong in
.codex/config.toml. Use itsdeveloper_instructionsonly for short Codex-specific behavioral additions; keep shared behavior in this file. - Prefer a tool-neutral intent here over parallel tool recipes. For example, say what evidence is required, then let each agent use its closest native capability. Create a tool-specific delta only when the behaviors genuinely cannot be the same.
Repository contract
- ccstory is a local-first Python 3.11+ CLI and library that turns Claude Code, Codex, and Antigravity session logs into recaps, trends, JSON, and read-only MCP results.
- Preserve behavior across every user-facing surface affected by a change: terminal cards, Markdown reports, JSON, trend/comparison output, and MCP.
- Keep provider-specific parsing under
ccstory/providers/. Shared attribution, usage, pricing, recap, and rendering logic stays provider-neutral. - Never estimate token usage or infer a model when the source does not expose
authoritative values. Keep incomplete coverage and unknown prices explicit
through the existing
usage_coverageandunpriced_modelslanes. - Preserve the local-data boundary documented in
README.md. Do not add telemetry or send transcript content to metadata services.
Concurrent-agent safety
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 · 89 lines · 896 tokens per session scan A 56008d897f1a
ccstory AGENTS.md is an instructions file published in the GitHub repository atomchung/ccstory (43 stars, last pushed 3d ago), licensed MIT. It adds 896 tokens to every session, about $0.0045 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
tokenmaxxing AGENTS.md
Instructions for 851-labs/tokenmaxxing, covering repository instructions, effect error style, export style, conventions and cli output style.
cctray CLAUDE.md
Instructions for goniszewski/cctray, covering claude.md, build and development commands, open in xcode and build with cmd+b, or use command line, unit tests and in xcode: cmd+u for all tests.
claude-usage-panel CLAUDE.md
Instructions for fschmutz/claude-usage-panel, covering claude.md, what this is, commands, ci - one required check, never edit branch protection and architecture - one contract, three ports.
ccusage-web CLAUDE.md
Instructions for jx453331958/ccusage-web, covering claude code project memory, common issues, project structure, deployment and agent.
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.