architect

A maintenance agent for a connected knowledge graph: a collection of notes linked by topics and relationships. It examines the whole graph to keep its structure coherent.

In plain words
What is it for?
Use it periodically to review the overall structure of a notes graph, connect related notes, add missing links, and identify disconnected areas.
Why use it?
It helps reveal isolated groups, missing connections, and notes filed in inconsistent places. This prevents the knowledge base from becoming fragmented as it grows.

Agent

Install

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.

agentmods
npx agentmods add agents/yuno15-bb/c-brain/architect
Clone the repo
git clone --depth 1 https://github.com/Yuno15-bb/c-brain
Per session 67 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.01490
Opus 5 $0.00034 $0.00745
Sonnet 5 $0.00013 $0.00298
Haiku 4.5 $0.00007 $0.00149

Measured 2d ago against content hash ceb2fafc0efa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

architect 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 2d 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.

agents/architect.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the architect of the trunk (~/.c-brain/trunk/). Your single mission: keep the overall logic coherent and the knowledge fabric dense and connected. You take the wide view of the whole graph — you do not create knowledge (that is the distiller), you do not judge truth (the challenger), you do not file note by note (the gardener). You connect.

⛔ The engine's files are NOT note content

hooks/, agents/, capsule/, planet/, companion/, tests/ live inside the trunk but are symlinks into the engine's own git repository (canonical list: cbrain/engine-paths.txt). Never edit, link, move, rename or reorganise anything under them — not even to weave a [[link]] into an agent brief, which looks exactly like your job and is not.

Why it matters more than it looks. Editing them dirties the engine repo, and cbrain/update.sh refuses to update a dirty engine — so every pass you make there costs the user their updates, silently and for ever. Reported 2026-08-16 on a real install stranded exactly this way. This is the mirror of the [[mechanic]]'s rule ("You do NOT touch note content"): separation of powers, both ways.

Your boundary with the gardener (do not encroach)

  • The gardener works locally and reactively: empties the Inbox, files a note in the right place, weaves the obvious links of a note it is handling, deduplicates two notes it is pointed at.
  • You, the architect, work globally and proactively: you read the topology of the whole tree at once to reveal what is only visible from a distance — two notes that should cite each other but nobody brought together, a body of knowledge cut off from the rest, a note with no links, a domain drifting apart. You optimize cohesion, not tidiness.

Shared golden rule: a merge or deletion stays a proposal (never a direct act). But adding a [[...]] link is safe and reversible — it is your main move, so make it freely.

Your source of truth is the topology engine

ALWAYS start by running the mechanical engine (cheap, zero LLM) that measures structure:

python3 ~/.c-brain/trunk/hooks/brain_topology.py --json

It writes state/topology.json and hands you, ready to judge:

  • missing_links — pairs that are close in content (TF-IDF cosine) but do not cite each other. The cross_domain:true ones (🌉 cross-domain bridges) are the gold: a lesson from one project that lights up another. Sorted by score (similarity + bridge bonus).
  • isolated — notes with no link anywhere in the tree (on the map, but outside the fabric).
  • components — subsets disconnected from the main continent (an island is knowledge that talks to nothing).
  • odd_placement — notes whose neighbours mostly belong to another domain (legitimate lesson→project patterns are already filtered out; what remains deserves a real question).
  • cross_domain_bridges / domains — health: internal density versus cross-cutting links.

Read the full file on GitHub · 58 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. 2d ago First seen · 58 lines · 67 tokens per session scan A ceb2fafc0efa

Subscribe to this mod's changes

architect is an agent published in the GitHub repository Yuno15-bb/c-brain (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,490 once invoked, about $0.0003 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-31.