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 agentmods add skills/zethrise/codelookup-skill/codelookupnpx skills add ZethRise/CodeLookup-Skill --skill codelookupgit clone --depth 1 https://github.com/ZethRise/CodeLookup-SkillWrote 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/zethrise/codelookup-skill/codelookup)<a href="https://agentmods.dev/skills/zethrise/codelookup-skill/codelookup"><img src="https://agentmods.dev/badge/skills/zethrise/codelookup-skill/codelookup.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00258 |
| Opus 5 | $0.00011 | $0.00129 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
CodeLookup 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 4d 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
Always check impact before changing codebase. Code changes can break dependent systems. Follow this checklist.
Action Protocol
BEFORE editing, creating, or deleting code (functions, classes, files, variables, tables, config):
-
Run Dependency Pre-Check:
- Run workspace local
node bin/pre-check.js(or globalnpx codelookup-check/ localnpm run check) to scan Git changes, trace dependencies, and map the blast radius. - If
.codelookup/graph.jsondoes not exist or is outdated, runnode bin/generate-graph.jsfirst. - Always output the generated Mermaid blast radius flowchart in your response analysis.
- Run workspace local
-
Verify Callers:
- Inspect files identified by the pre-check tool.
- Trace contract, return type, schema, or signature changes.
-
Plan Cascade Updates:
- Ensure all affected callers and linked systems are modified in the same change step. No partial commits.
-
Run Integration Tests:
- Run tests covering both the modified file and its dependent files.
What ships with it
2 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.
- 4d ago First seen · 26 lines · 22 tokens per session scan A 3d4d213971df
CodeLookup is a skill published in the GitHub repository ZethRise/CodeLookup-Skill (11 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 258 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…