What is growmos AGENTS.md?

Repository instructions for growmos, a tool that keeps a shared knowledge graph as project memory in the .growmos/ folder. The graph records things such as entities, relationships, sources, profiles, and journal entries.

Use it to load a project brief, investigate dependencies or past decisions, and save facts, ownership details, architectural choices, and lessons learned.

It helps coding agents retain important project knowledge between sessions and context limits. It also gives them a consistent way to look up decisions and record new durable information.

How codician-team/growmos configures Codex and OpenCode

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/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/codician-team/growmos

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/codician-team/growmos/agents-md/github.svg)](https://agentmods.dev/instructions/codician-team/growmos/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/codician-team/growmos/agents-md"><img src="https://agentmods.dev/badge/instructions/codician-team/growmos/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/codician-team/growmos/agents-md"><img src="https://agentmods.dev/badge/instructions/codician-team/growmos/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 606 This file is loaded in full into every session.

When invoked 606 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00606	$0.00606
Opus 5.5	$0.00242	$0.00242
Sonnet 5.5	$0.00121	$0.00121
Haiku 4.5	$0.00061	$0.00061

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

Security

Grade A, and why

growmos 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 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

Copies of this mod

1 near-identical copy found in the catalogue:

growmos CLAUDE.md — 97% identical, 2 lines differ

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

AGENTS

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

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.

2mo ago First seen · 34 lines · 606 tokens per session scan A 059ab0a46ef1

Subscribe to this mod's changes

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

Memory and context agent agent-memory agent-orchestration agent-skill agent-skills agentic

growmos AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
growmos AGENTS.mdcodician-team/growmos	Instructions file	9	2mo ago	MIT	A	606	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

growmos: Instructions file for Codex