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 AuraVixStudio/caelo --skill explain-codebasegit clone --depth 1 https://github.com/AuraVixStudio/caeloWrote 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/auravixstudio/caelo/explain-codebase)<a href="https://agentmods.dev/skills/auravixstudio/caelo/explain-codebase"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/explain-codebase/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/auravixstudio/caelo/explain-codebase"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/explain-codebase.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.00017 | $0.00282 |
| Opus 5.5 | $0.00007 | $0.00113 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
Explain codebase 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.
What it actually says
Explain codebase
Use this when the user wants to understand how a project or module works.
Steps
- Orient. Find the entry points, the build/run commands, and any README/architecture docs. Identify the main directories and what each is responsible for.
- Trace a path. Pick a representative flow (a request, a command, a feature) and follow it across files. Concrete paths explain a system better than abstractions.
- Map the pieces. Note the key modules, the data model, and how components talk to each other (calls, events, HTTP, queues).
- Explain. Summarize for the user: the big picture first, then the important
components, then the one flow you traced — with clickable
file:linereferences. - Point forward. Call out where to look to change X, and any sharp edges or conventions worth knowing.
Notes
- Read before asserting. Verify names/paths exist rather than inferring from memory.
- Tailor depth to the user's question — don't dump the whole tree.
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 · 28 lines · 17 tokens per session scan A 033fca0f82f3
Explain codebase is a skill published in the GitHub repository AuraVixStudio/caelo (25 stars, last pushed 5d ago), licensed Apache-2.0. It adds 17 tokens to every session and 282 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-30.
Other skills, from other repositories
skill-creator
A guide for creating and maintaining skills for Lfcode, including where to store them and which files each skill needs.
tavern-management
Use when the user asks to import or translate an Lfcode Tavern or SillyTavern character card or worldbook, including PNG image cards, or manage the Tavern plugin lifecycle.
error-collection
A structured record of confirmed engineering mistakes, their root causes, and checks that prevent them from returning. It uses evidence from real application behavior, not just successful builds.
playwright-browser
Use when controlling browser pages with Playwright MCP in Lfcode; guides navigation, screenshots, interaction, and reuse of hidden or collapsed embedded side browser targets instead of the Electron app shell.
accessibility-auditor
Use when the user asks to audit accessibility, keyboard usability, semantics, contrast, focus behavior, or assistive-technology support in a UI. Inspect the actual rendered page and interaction states, report evidence-backed findings, and only implement fixes when explicitly requested.
codebase-explorer
Use when the user asks to understand, map, trace, or locate behavior in an unfamiliar repository. Inspect the actual code, configuration, runtime entrypoints, and tests before proposing changes; stay read-only unless a change is explicitly requested, and report evidence and remaining uncertainty.