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 skills add wei6bin/skills --skill codebase-context-buildergit clone --depth 1 https://github.com/wei6bin/skillsWrote 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/skills/wei6bin/skills/codebase-context-builder)<a href="https://agentmods.dev/skills/wei6bin/skills/codebase-context-builder"><img src="https://agentmods.dev/badge/skills/wei6bin/skills/codebase-context-builder/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.
<a href="https://agentmods.dev/skills/wei6bin/skills/codebase-context-builder"><img src="https://agentmods.dev/badge/skills/wei6bin/skills/codebase-context-builder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00030 | $0.00989 |
| Opus 5.5 | $0.00012 | $0.00396 |
| Sonnet 5.5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
codebase-context-builder 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Context Builder
Context generation only. Return control when done; do not proceed to story analysis.
Analyse the root you were given: the current checkout, or the worktree
project-scaffolder works in. A freshly scaffolded repo is a walking skeleton,
and two things change:
project-scaffolderhands you the conventions established by each scaffolded layer. Write each into the file for its layer as the project's rule, and list in00_index.md, under "Overrides of the house skills", every one that differs fromrestful-api-designorreact-best-practices; project conventions win there, and the architect andimpl-simplifyread this folder before applying either.- The only domain is the skeleton's auth (users, sessions, audit log). Mark the
business sections of
02_domain_model.md[TODO: first story]rather than inventing a domain.
Analyse
- Stack: read manifests (
package.json,*.csproj/*.sln,pyproject.toml/requirements.txt,pom.xml/build.gradle,go.mod), Dockerfiles/compose, CI files,CLAUDE.md/AGENTS.md/README.md. Extract languages, frameworks, build/test/run scripts, key dependencies (UI lib, ORM, test framework, state), deployment target. - Structure: map source directories 2-3 levels deep (skip
node_modules, build output). Identify feature modules, shared code, API/service/data layers, test layout. - Conventions: sample 2-3 files per layer (endpoints, services, repositories, models/DTOs, UI components) and extract naming, imports, error handling, DTO shape, DI usage.
- Domain: read 3-5 core model files; extract entities, key fields, relationships, lifecycle states.
Generate docs/project_context/
Always:
00_index.md- task-to-file lookup with actual file references01_architectural_overview.md- layers, patterns, tech found02_domain_model.md- entities and workflows inferred from code04_build_environment.md- how the dev loop actually runs, because a hot-reload rebuild that contends with an implementer's edit onobj/or.vite/deps/looks like a product bug ("API is dead"). Seed, marking[TODO: confirm]where uncertain: hot-reload runner (host/containerdotnet watch,vite, none); rebuild-trigger globs; binary-lock paths during rebuild; multi-file edit recipe (pause the watcher,--no-restore,--no-hot); each shared dev service (db, api, redis) with its non-destructive restart, neverdocker compose down -v.
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.
- 10d ago Changed · +10 lines 1b1df5d191f2
- 17d ago Changed · -69 lines · -30 tokens per session 8c97fa4ca719
- 24d ago Changed · -28 lines · -1 tokens per session 099cb511838e
- 1mo ago First seen · 175 lines · 61 tokens per session scan A 73310e1ef291
codebase-context-builder is a skill published in the GitHub repository wei6bin/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 989 once invoked, about $0.0001 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.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
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…
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.
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…
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.