agentmods.dev

explain_codebase

A workflow for inspecting a software project's folders, entry points, and configuration files, then explaining how the codebase is organized and run.

In plain words
What is it for?
Use it to identify a project's languages, frameworks, architecture, important starting files, and run instructions.
Why use it?
It gives you a quick map of an unfamiliar project instead of requiring you to discover its structure file by file. The input does not specify which programming languages or frameworks it supports.

Skill for Claude CodeCodex

5 7d ago A scan 0 tokens original MIT
View the source file ahmadrrrtx/xr
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 skills/ahmadrrrtx/xr/explain_codebase
Any agent
npx skills add ahmadrrrtx/xr --skill explain_codebase
Clone the repo
git clone --depth 1 https://github.com/ahmadrrrtx/xr

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 84 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.00000 $0.00084
Opus 5 $0.00000 $0.00042
Sonnet 5 $0.00000 $0.00017
Haiku 4.5 $0.00000 $0.00008

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

Security

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 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.

skills/explain_codebase/SKILL.md · 13 lines

What it actually says

Explain Codebase

  1. list_dir from the root to map structure.
  2. read_file entry points + config files.
  3. Summarize: languages, frameworks, architecture, how to run.
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 · 13 lines · 0 tokens per session scan A 58881ccbf51d

Subscribe to this mod's changes

explain_codebase is a skill published in the GitHub repository ahmadrrrtx/xr (5 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 84 tokens. 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.

PlanningProductivityai-agentai-agentsbunbyokbyok-ai-tools-code-assistantllms
Related

Other skills, from other repositories

brainllm

Persistent memory and knowledge graph via the BrainLLM (Trilium) MCP. Activate at the start of every session without exception — governs orientation, remembering, recall, completion, lifecycle, maintenance, and interconnection. Trigger immediately on any first user message. Also trigger whenever: memory is referenced…

miisodev/BrainLLM · 115 tokens

cuj-guardian

Run and triage AI Atelie's Critical User Journey (CUJ) for every PR — the single end-to-end test that proves a user can open the app, create a project, drive the Claude Code agent, and see the canvas render. Before running, gate by inspecting the PR diff for changes that plausibly affect the journey (routes…

aiatelie/ai-atelie · 137 tokens

ship-task

Take an AI Atelie task — issue, ticket, or ad-hoc ask — all the way from description to merged-ready PR. Use whenever the user says "implement X and ship it", "work on issue.

aiatelie/ai-atelie · 46 tokens

canvas-sync

Keep the canvas surface coherent across its three places — the canonical starter at mcp/starters/DesignCanvas.jsx, the byte-identical demo copy at web/projects/demo/design-canvas.jsx, and the host-side wiring in web/src/lib/tweakBridge.ts plus mcp/CANVASPROTOCOL.md. Use whenever the diff touches any of those files, or…

aiatelie/ai-atelie · 147 tokens

export

Export a selected element from the canvas as PNG, JPEG, OGraf bundle, Lottie, or video. Saves to the project's exports/ folder; the chat renders the result inline as an artifact card.

aiatelie/ai-atelie · 43 tokens

pr-evidence

Run AI Atelie's journey suite and inject inline-rendering evidence (per-journey video + screenshot, in a 4-column markdown table) into the current PR's body. Use whenever the user says "post evidence", "run journeys", "update PR with videos", or after ship-task opens a PR. Wraps bun run journeys; idempotent — re-runs…

aiatelie/ai-atelie · 93 tokens