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 jszmajda/lid --skill map-codebasegit clone --depth 1 https://github.com/jszmajda/lidWrote 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/jszmajda/lid/map-codebase)<a href="https://agentmods.dev/skills/jszmajda/lid/map-codebase"><img src="https://agentmods.dev/badge/skills/jszmajda/lid/map-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/jszmajda/lid/map-codebase"><img src="https://agentmods.dev/badge/skills/jszmajda/lid/map-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.03063 |
| Opus 5.5 | $0.00037 | $0.01225 |
| Sonnet 5.5 | $0.00018 | $0.00613 |
| Haiku 4.5 | $0.00009 | $0.00306 |
Grade A, and why
map-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 5d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Codebase (Brownfield Arrow Bootstrap)
This skill maps an existing codebase into the arrow of intent. It works bottom-up: read all the code in scope first, then propose lens-based clusterings for the user to choose among, then generate skeleton docs that describe what actually exists.
See brownfield-bootstrap.md for detailed guidance per phase.
Five Critical Rules
These govern every phase. Apply consistently.
- Read actual code, don't guess. Every claim in generated artifacts traces to file/line evidence. Speculation is flagged explicitly rather than presented as fact.
- Each STOP is mandatory. The workflow has multiple stop points. None are optional. Rushing past a stop is how brownfield mapping produces bad LLDs that poison subsequent work.
- LLDs describe current reality, not aspirational design. Output is what the code is, not what a greenfield version would be. Inferred design decisions carry
[inferred]markers; known technical debt and behavioral quirks go in Open Questions. - Thoroughness over speed. Token budget is real but not dominant; skimming produces mappings that miss behaviors and lock in the wrong segmentation.
- Humble but guide. The agent is not the expert on the user's system; the user is. But don't silently defer — when the user's framing conflicts with the evidence, surface the tension with evidence rather than just going along.
At invocation
Ask one question first:
- Whole project, or specific parts?
- Whole project → implies Full LID mode. Scope is the entire project.
- Specific parts → implies Scoped LID mode. Ask the user to name the parts (directories, file lists, or component names). The declared parts are both the sweep scope and the LID scope going forward.
This question determines scope and mode simultaneously — the user is not asked a separate "Full or Scoped?" later at terminal verification. Default to Full (whole project) if the user is undecided.
What ships with it
5 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.
- 5d ago Changed b75cbed222e0
- 1mo ago First seen · 160 lines · 92 tokens per session scan A d463d0b6d0af
map-codebase is a skill published in the GitHub repository jszmajda/lid (112 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 3,063 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-30.
Other skills, from other repositories
user-docs
Write user documentation for a project by scanning its codebase — its UI screens and its public API/CLI — inferring what someone can actually do with it, and drafting brief, task-oriented docs to the Diátaxis standard (tutorial / how-to / reference / explanation). Handles both non-technical end-user docs and developer…
add
Create a new Clawness rule from a natural language description. Describe what you want enforced and this will generate the YAML rule file with proper tags, triggers, and examples.
messaging
Write or rewrite the product's customer-facing copy — landing page, hero section, CTAs, onboarding, empty states, pricing, app-store and marketing pages — with the customer as the hero and the product as their guide. Scans the existing UI copy, drafts a one-page message brief (who the customer is, what they want, the…
review
Run an adversarial code review on staged changes or a specific file. Spawns the code-critic agent to find bugs, performance issues, and missed edge cases. Use before merging PRs or committing.
perf
Run a performance audit on the project or a specific module. Checks for N+1 queries, unnecessary re-renders, memory leaks, bundle size issues, and slow algorithms.
oneshot
End-to-end autonomous workflow — research, plan, implement, validate, ship, and merge in one command. ALWAYS use when the user says 'oneshot', 'do everything end to end', 'full workflow', or wants to go from ticket/idea to merged PR autonomously. All phases run sequentially in the current session, using agent teams…