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/codician-team/growmos/claude-mdgit clone --depth 1 https://github.com/codician-team/growmosWrote 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/codician-team/growmos/claude-md)<a href="https://agentmods.dev/instructions/codician-team/growmos/claude-md"><img src="https://agentmods.dev/badge/instructions/codician-team/growmos/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 | $0.00607 | $0.00607 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
growmos 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 4d 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.
This is a copy
97% identical to growmos AGENTS.md — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE
growmos — living knowledge graph (shared memory for humans + agents)
This repository keeps a knowledge graph in .growmos/ (entities, typed relations, provenance,
profiles, a journal). It is the shared world model that survives context windows. Treat it as
memory you read at the start of work and write to as you develop. Zero-config commands:
- Session start — run
growmos context(a compact brief: hubs, health, pending work, latest journal). If it lists pending work, run thegrowmos next→ apply loop (step 4) right away, without being asked — it is quick, needs no permission, and is how the graph stays alive. - Before cross-cutting questions ("what depends on X?", "why was Y decided?") — run
growmos query "<question>"; answer from the returned subgraph and cite edge ids. - When you learn or decide something durable (new component, architectural decision, ownership,
dependency, gotcha) — write it back immediately:
growmos remember "<Name>" --type <TYPE> --desc "<one grounded sentence>"growmos link "<A>" "<predicate>" "<B>"(short verb phrase predicates: "depends on", "replaces")growmos journal "<what changed and why>"
- Feed the organism — run
growmos next. It hands you a task packet (extraction / resolution / profile / gold set / review) with the exact prompt, the JSON shape, and thegrowmos apply …command. Do the judgment work yourself, write the JSON, apply it. Repeat untilgrowmos nextsays the graph is up to date — that loop covers everything, including the evaluation gold set and the periodic node review. If it reports the daily extraction cap, rungrowmos next --force(the cap only guards unattended runs). Never invent facts not in the source; every relation must connect two extracted entities. - Before claiming facts about the repo in a summary/report —
growmos check "<claim text>"grounds your claims against edges with provenance (evaluator–optimizer loop). - Session end —
growmos journal "<summary of the session>"so the next session picks up here.
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.
- 4d ago First seen · 34 lines · 607 tokens per session scan A 2889e4342b2d
growmos CLAUDE.md is an instructions file published in the GitHub repository codician-team/growmos (9 stars, last pushed 18d ago), licensed MIT. It adds 607 tokens to every session, about $0.0030 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to growmos AGENTS.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
build_a_product_agent CLAUDE.md
Instructions for ADW-19/build_a_product_agent, covering claude.md, 项目本质（readme 概览之外）, 目录与编号规范, 文章写作规范（新增/修改文章时必须遵循） and 常用操作.
akidevrule GEMINI.md
Instructions for lacvietanh/akidevrule, covering gemini.md — ag rules bootstrap, 1. single source of truth and 2. separation of concerns.
akidevrule CLAUDE.md
Instructions for lacvietanh/akidevrule, covering akidevrule, project role, source of truth, file naming conventions and rule authoring principles.
starfleetctl AGENTS.md
AGENTS.md instructions for mpbt-hq/starfleetctl, a project described as: multi agent coordination / command & control toolkit following the Startrek fleet metaphor.
beevibe CLAUDE.md
Claude Code instructions for beevibe-ai/beevibe, covering beevibe — claude code guide, monorepo structure, running locally, critical: @beevibe/core compiles to dist/ and restarting cleanly.
pi-agent-dashboard AGENTS.md
AGENTS.md instructions for BlackBeltTechnology/pi-agent-dashboard, covering pi dashboard, docs-first gate — kb before grep (per-turn doctrine), code instructions (per-turn doctrine), investigation protocol — index first and documentation update protocol.