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 kouroshez/coding-os --skill codebase-explorergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/codebase-explorer)<a href="https://agentmods.dev/skills/kouroshez/coding-os/codebase-explorer"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/codebase-explorer/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/kouroshez/coding-os/codebase-explorer"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/codebase-explorer.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.00092 | $0.00887 |
| Opus 5.5 | $0.00037 | $0.00355 |
| Sonnet 5.5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
codebase-explorer 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore the specified conceptual area of the codebase and produce a structured map. Boundary with graph-explorer:
| Question shape | Use |
|---|---|
| "How does X work end-to-end?" | codebase-explorer |
| "What happens when a user does Y?" | codebase-explorer |
| "Where does this domain live?" | codebase-explorer |
"What calls function foo?" |
graph-explorer (cos_graph_references) |
"What breaks if I rename Bar?" |
graph-explorer (cos_graph_rename_plan) |
"Blast radius of changing baz?" |
graph-explorer (cos_graph_impact) |
codebase-explorer always consults graph-explorer for symbol-precise sub-questions during a conceptual walk — they compose, they don't compete.
Process
- Graph gate — If the query is an identifier-shaped symbol
(
camelCase,snake_case,Class.method,TASK-NNN, dotted path), trycos_graph_queryfirst. It is faster + more accurate than grep for named symbols AND returns confidence-scored edges. Fall back to grep only if the graph returns zero hits (fresh repo, unindexed file) or the query is conceptual ("auth flow", "money handling"). - Entry points — Use Grep to find the main files related to the topic.
- Trace the flow — Read key files, follow imports. When symbols
cross file boundaries, prefer
cos_graph_context(uid, depth=1)over chasing imports by hand — it returns the neighbourhood in a single MCP call. - Dependencies — Identify what this area depends on (models,
services, external APIs). For impact analysis, use
cos_graph_impact(uid, direction="downstream")— the plan's Formula-2 Step-10 tool. - Test coverage — Use Glob to find related test files. Graph edges
of type
tested_by(when present) point directly at them.
Output Format
Return a structured summary:
## [Area Name] — Codebase Map
### Entry Points
- file:line — description
### Data Flow
source → transform → destination
### Key Files
- path — responsibility
### Dependencies
- internal: models, services used
- external: APIs, packages
### Test Coverage
- test files found
- gaps identified
### Risks
- anything fragile, tightly coupled, or undocumented
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 90 lines · 92 tokens per session scan A 7d8aa2428e24
codebase-explorer is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 92 tokens to every session and 887 once invoked, about $0.0004 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
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, resource (document payload) commands, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
analyze-type-infer
A compiler analysis step that infers a symbol's type from its assignments. A type describes what kind of value something holds, such as a number, text, or Boolean value.
check-name-real
A name checker that verifies every required symbol has been declared. A symbol is a named program entity such as a variable or function.
compiler-0355bffb
A virtual-machine debugging skill for executing one instruction at a time. A virtual machine is a program that runs a compact instruction format instead of native machine code.
compiler-2dbea54a
A cycle-detection skill that checks a directed graph for loops using depth-first search, a method that follows each path before backtracking.