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/jimmypaolini/codebase/codependix-exportnpx skills add JimmyPaolini/codebase --skill codependix-exportgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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.00121 | $0.01740 |
| Opus 5 | $0.00060 | $0.00870 |
| Sonnet 5 | $0.00024 | $0.00348 |
| Haiku 4.5 | $0.00012 | $0.00174 |
Grade A, and why
codependix-export 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 yesterday.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running a codependix export
Codependix reads what each project in an Nx workspace depends on and renders it four ways — the Nx project graph, a NestJS project's module graph, a TypeScript project's file-level import graph, and a Python project's — then delivers each one to whichever destinations the configuration names for that project: a JSON file, a Markdown anchor block spliced into an existing file, or both.
The configuration decides everything
There is no flag that selects a graph type, and no per-graph-type
subcommand. Which graphs run, for which projects, and where each export
lands is entirely a function of codependix.config.ts. Looking for
--nestjs, --imports, or --only nx is looking for something that does not
exist.
The corollary is the failure mode worth learning first:
A workspace with no configuration file resolves every graph type for every project to
target: "none"and produces nothing. The run succeeds, exits 0, logs that every configured export is current, and writes no files — because nothing was configured. That is correct behavior, not a bug.
So a --write that wrote nothing is a configuration question, never a
debugging one. Before looking for a defect, confirm in this order:
- A configuration file was actually found — an absent one is legal and
silent, while a
--configpath that was named explicitly and does not exist fails loudly. - The graph types you expected carry a
targetother than"none", which is what every unset target defaults to. - The projects you expected match the configured
includeglobs and noexcludeglob.
The codependix-configure skill covers all three.
Exactly two run modes
| Mode | Meaning |
|---|---|
--check |
Verifies every configured export is current, writing nothing |
--write |
Writes every configured export |
--check and --write are mutually exclusive, and one of them is
required. A command line naming neither, or both, is rejected outright
before anything is read — no mode is inferred and no default write happens.
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.
- yesterday First seen · 162 lines · 121 tokens per session scan A 6831adefb6ac
codependix-export is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 1,740 once invoked, about $0.0006 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-09-01.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.