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 lfyxhappy/lfcode --skill codebase-explorergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/codebase-explorer)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/codebase-explorer"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/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/lfyxhappy/lfcode/codebase-explorer"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/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.00059 | $0.00361 |
| Opus 5.5 | $0.00024 | $0.00144 |
| Sonnet 5.5 | $0.00012 | $0.00072 |
| Haiku 4.5 | $0.00006 | $0.00036 |
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.
What it actually says
Codebase Explorer
Build an evidence-based map of the repository before drawing conclusions.
Workflow
- Establish the repository root, applicable
AGENTS.mdfiles, package boundaries, and the user's requested scope. - Check
git status, the current branch, and relevant diffs. Preserve unrelated user changes. - Inventory files with
rg --files, then inspect manifests, entrypoints, configuration, scripts, and the tests closest to the behavior. - Trace the requested symbol or data through callers, persistence, APIs, and runtime consumers with
rg. Follow the real execution path instead of relying on names alone. - When runtime behavior matters, run the smallest safe diagnostic or inspect the actual response, logs, or generated artifact.
- Report concrete file paths and line locations, separating confirmed facts, likely inferences, and unanswered questions.
Boundaries
- Treat an exploration request as read-only. Do not edit files, install dependencies, commit, push, or contact external services unless the user explicitly asks.
- Do not infer that a source change is deployed or that a build artifact is current without checking the process, path, timestamp, or response that uses it.
- Avoid dumping credentials, cookies, tokens, personal data, or unredacted request bodies into notes or the final report.
Completion check
End with the discovered entrypoints, important dependencies, relevant tests, and the narrowest next action. State what was not verified.
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 · 59 tokens per session scan A 86c005325a9c
codebase-explorer is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 26d ago), licensed MIT. It adds 59 tokens to every session and 361 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
Debug (reproduce -> isolate -> fix)
Systematically diagnose and fix a bug instead of guessing.
feishu-troubleshoot
A Feishu troubleshooting tool with FAQs and diagnostic commands. Feishu is a collaboration platform with online documents and workplace services.
investigate
A structured root-cause investigation method for software bugs. It moves from history and reproduction through tested hypotheses, a focused fix, verification, and a report.
bugfix-triage
A method for locating the cause of a bug before changing code, using a minimal reproduction and step-by-step narrowing of the failing input and code path.
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
business-ops-runbook-generator
Build an operational runbook with rollback paths for a recurring task or incident: capture the brief, infer failure modes, draft the runbook steps and checks, then define a rollback path for each failure mode. Use when the user wants a step-by-step runbook that an operator can follow under pressure, including what to…