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/jaybocc2/dotfiles/code-reviewnpx skills add jaybocc2/dotfiles --skill code-reviewgit clone --depth 1 https://github.com/jaybocc2/dotfilesWhat 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.00011 | $0.00375 |
| Opus 5 | $0.00005 | $0.00187 |
| Sonnet 5 | $0.00002 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
code-review 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 today.
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
If no issues are found:
Change summary: [Single sentence description of the overall change].
No issues found. Code looks clean and ready to merge.
If issues are found:
Change summary: [Single sentence description of the overall change].
[Optional general feedback for the entire change, e.g., unrelated change that should be in a different PR, or improved general approaches.]
File: path/to/file/one
L<LINE_NUMBER>: [] Single sentence summary of the issue.
More details about the issue, including why it is an issue (e.g., "This could lead to a null pointer exception").
Suggested change:
while (condition) {
unchanged line;
- remove this;
+ replace it with this;
+ and this;
but keep this the same;
}
L<LINE_NUMBER_2>: [MEDIUM] Summary of the next problem.
More details about this problem, including where else it occurs if applicable (e.g., "Also seen in lines L45, L67 of this file.").
File: path/to/file/two
L<LINE_NUMBER_3>: [HIGH] Summary of the issue in the next file.
Details...
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.
- today First seen · 49 lines · 11 tokens per session scan A f9897dbfd874
code-review is a skill published in the GitHub repository jaybocc2/dotfiles (11 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 375 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-09-02.
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…