repo-architecture

repo-architecture is a skill for Claude Code, Codex from garrytan/gbrain. It costs 34 tokens per session (419 once invoked), scanned A, original, MIT.

A set of rules for deciding where new knowledge-base pages belong, based on the main subject rather than the file format or where the information came from.

In plain words
What is it for?
Use it to place pages about people, companies, concepts, ideas, meetings, media, and raw imported data in the appropriate folders.
Why use it?
It prevents duplicate, misplaced, or hard-to-find pages by applying one consistent filing decision.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Part of the gbrain-coding plugin — 20 skills shipped together

Good fit Use it to place pages about people, companies, concepts, ideas, meetings, media, and raw imported data in the appropriate folders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/garrytan/gbrain/repo-architecture
About the project

GBrain is a memory and retrieval layer for AI agents that searches, connects, and synthesizes information from stored sources. It is used to give coding agents and autonomous agents access to knowledge beyond their current code, including shared company information with access controls. The catalogue add-ons help agents operate GBrain and connect it to agent workflows.

garrytan/gbrain · 29,838 stars · on GitHub

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.

Any agent
npx skills add garrytan/gbrain --skill repo-architecture
Clone the repo
git clone --depth 1 https://github.com/garrytan/gbrain

Made for: Claude Code, Codex.

Or install gbrain-coding, the plugin that ships this one along with the rest of its 20 skills.

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 repo-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/garrytan/gbrain/repo-architecture/github.svg)](https://agentmods.dev/skills/garrytan/gbrain/repo-architecture)
Your own site
<a href="https://agentmods.dev/skills/garrytan/gbrain/repo-architecture"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/repo-architecture/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 repo-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/garrytan/gbrain/repo-architecture"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/repo-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 419 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 52
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.1 $0.00034 $0.00419
Opus 5 $0.00017 $0.00210
Sonnet 5 $0.00007 $0.00084
Haiku 4.5 $0.00003 $0.00042

Measured 12d ago against content hash 4ec2b8f45d16, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

repo-architecture 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 12d 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

2 near-identical copies found in the catalogue:

plugin-variants/gbrain-coding/skills/repo-architecture/SKILL.md · 54 lines

What it actually says

Repo Architecture — Filing Rules

Full filing rules: See skills/_brain-filing-rules.md

Contract

This skill guarantees:

  • Every new page is filed by primary subject (not format, not source)
  • The decision protocol is followed for ambiguous cases
  • Common misfiling patterns are caught

Phases

  1. Identify the primary subject. What would you search for to find this page?
  2. Walk the decision tree:
    • About a person → people/{name-slug}.md
    • About a company → companies/{name-slug}.md
    • A reusable concept/framework → concepts/{slug}.md
    • An original idea → originals/{slug}.md
    • A meeting → meetings/{slug}.md
    • Media content → media/{type}/{slug}.md
    • Raw data import → sources/{slug}.md
  3. Cross-link. Link from related directories.
  4. Check notability. See skills/conventions/quality.md notability gate.

Output Format

Advisory: "File this at {type}/{slug}.md because the primary subject is {reason}."

Anti-Patterns

  • Filing by format ("it's a PDF so it goes in sources/")
  • Filing by source ("it came from email so it goes in sources/")
  • Creating pages without checking if one already exists
  • Using sources/ for anything except raw data dumps
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. 12d ago First seen · 54 lines · 34 tokens per session scan A 4ec2b8f45d16

Subscribe to this mod's changes

repo-architecture is a skill published in the GitHub repository garrytan/gbrain (29,838 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 419 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens

establishing-project-context

Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.

GanyuanRan/Aegis · 45 tokens

shellm

Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.

laude-institute/headlong · 49 tokens