growmos: Instructions file for Claude Code

CLAUDE.md

growmos CLAUDE.md is an instructions file for Claude Code from codician-team/growmos. It costs 607 tokens per session, scanned A, a copy of growmos AGENTS.md, MIT.

Instructions for maintaining a knowledge graph: a connected record of entities, relationships, sources, decisions, and notes stored in a repository.

In plain words
What is it for?
Use it at session start, when investigating cross-cutting questions, and when recording components, ownership, dependencies, decisions, or pitfalls.
Why use it?
It preserves important project knowledge between work sessions and helps answer questions about dependencies and past decisions.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is codician-team/growmos's own configuration. It tells Claude Code how to work on growmos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything growmos configures →

Reuse

Borrowing it

Nothing to install: this file belongs to codician-team/growmos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/codician-team/growmos/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/codician-team/growmos

Made for: Claude Code.

Wrote 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.

agentmods badge for growmos CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/codician-team/growmos/claude-md/github.svg)](https://agentmods.dev/instructions/codician-team/growmos/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/codician-team/growmos/claude-md"><img src="https://agentmods.dev/badge/instructions/codician-team/growmos/claude-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.

agentmods 80×15 button for growmos CLAUDE.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 607 This file is loaded in full into every session.
When invoked 607 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00607 $0.00607
Opus 5.5 $0.00243 $0.00243
Sonnet 5.5 $0.00121 $0.00121
Haiku 4.5 $0.00061 $0.00061

Measured 2mo ago against content hash 2889e4342b2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

Origin

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.

CLAUDE.md · 34 lines

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:

  1. Session start — run growmos context (a compact brief: hubs, health, pending work, latest journal). If it lists pending work, run the growmos next → apply loop (step 4) right away, without being asked — it is quick, needs no permission, and is how the graph stays alive.
  2. 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.
  3. 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>"
  4. 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 the growmos apply … command. Do the judgment work yourself, write the JSON, apply it. Repeat until growmos next says 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, run growmos next --force (the cap only guards unattended runs). Never invent facts not in the source; every relation must connect two extracted entities.
  5. Before claiming facts about the repo in a summary/report — growmos check "<claim text>" grounds your claims against edges with provenance (evaluator–optimizer loop).
  6. Session end — growmos journal "<summary of the session>" so the next session picks up here.

Read the full file on GitHub · 34 lines

Changes

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.

  1. 2mo ago First seen · 34 lines · 607 tokens per session scan A 2889e4342b2d

Subscribe to this mod's changes

growmos CLAUDE.md is an instructions file published in the GitHub repository codician-team/growmos (9 stars, last pushed 2mo ago), licensed MIT. It adds 607 tokens to every session, about $0.0024 per session on Opus 5.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.

Related

growmos CLAUDE.md compared with instructions from other repositories

growmos CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
growmos CLAUDE.mdcodician-team/growmosInstructions file92mo agoMITA607Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode