Borrowing it
Nothing to install: this file belongs to TheGreenCedar/CodeStory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheGreenCedar/CodeStory/main/AGENTS.mdgit clone --depth 1 https://github.com/TheGreenCedar/CodeStoryWrote 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/thegreencedar/codestory/agents-md)<a href="https://agentmods.dev/instructions/thegreencedar/codestory/agents-md"><img src="https://agentmods.dev/badge/instructions/thegreencedar/codestory/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/thegreencedar/codestory/agents-md"><img src="https://agentmods.dev/badge/instructions/thegreencedar/codestory/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.05246 | $0.05246 |
| Opus 5.5 | $0.02098 | $0.02098 |
| Sonnet 5.5 | $0.01049 | $0.01049 |
| Haiku 4.5 | $0.00525 | $0.00525 |
Grade A, and why
CodeStory 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 27d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodeStory Agent Guide
Audience: agents and contributors changing CodeStory. This file contains the decisions that must remain visible while working; generated help, architecture pages, runbooks, and workflows own detailed mechanics.
Start Here
- Before mutating the tree, creating a lane, or delegating work, inspect the
current branch, integration head, active worktrees, and open PR or issue
ownership. Inspect release state only for release work. Do not reuse an
active lane or implement routine work directly on
dev/codestory-next. - Run
node scripts/codex-worktree-setup.mjsfor a delegated worktree. Treat its printed base, child head, PR head, and proof target as authoritative before cache repair, readiness work, or verification. When changing setup, keep the PowerShell and POSIX implementations behaviorally aligned and run the setup self-tests from the testing matrix. - Use the canonical CodeStory grounding skill when its MCP tools are visible
and the task is repository discovery, relationship tracing, change-impact
analysis, or CodeStory retrieval / installed-plugin validation. Skip that
loop only for bounded inspection or editing of named files that does not
require those operations; naming a file does not by itself forbid CodeStory.
Every
MCP call must carry the target repository's absolute
projectroot. Call the tool that matches the task directly; tool gating owns readiness and managed preparation. Read status only after a call fails to converge. If the MCP tools are not visible, use ordinary source inspection and report the visibility gap. CLI diagnostics do not prove that the packaged plugin MCP is live in the agent host. Qualify CodeStory results as retrieval or installed-plugin evidence, not as live runtime behavior, unless the matching proof tier exists. - When a linked document path is already known, bound
rgor search to that file. Do not run a broad package or repository search merely to rediscover a documented path. - Route reading by the task: the owning architecture page (from
docs/architecture/overview.mdand the subsystem page) when contracts change,docs/contributors/debugging.mdfor failures, and the relevant lane indocs/contributors/testing-matrix.mdwhen selecting proof. Do not pre-read all four contributor docs for every large change.
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.
- 27d ago Changed · -4 lines · -252 tokens per session 8d9f4d32669c
- 1mo ago First seen · 402 lines · 5,498 tokens per session scan A 9013f5946ca2
CodeStory AGENTS.md is an instructions file published in the GitHub repository TheGreenCedar/CodeStory (37 stars, last pushed yesterday), licensed Apache-2.0. It adds 5,246 tokens to every session, about $0.0210 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.