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/validate-codenpx skills add JimmyPaolini/codebase --skill validate-codegit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/validate-code)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/validate-code"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/validate-code.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.00096 | $0.01900 |
| Opus 5 | $0.00048 | $0.00950 |
| Sonnet 5 | $0.00019 | $0.00380 |
| Haiku 4.5 | $0.00010 | $0.00190 |
Grade A, and why
validate-code 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Code
Run the codebase's full automated quality suite against your changes before committing. This prevents pre-commit hook failures, failed CI jobs, and wasted triage cycles.
When to Use This Skill
- After finishing implementation of any task — TypeScript, Python, Markdown, YAML, JSON
- Before invoking the submit-changes skill
- When asked to "validate", "check code quality", "run linting", or "verify changes are clean"
- Anytime you add new dependencies, exports, or files (Knip detects unused ones)
What lint-codebase Covers
The lint-codebase Nx target hangs every quality tool off dependsOn, so one invocation builds one task graph:
| Tool | Purpose | Configuration |
|---|---|---|
oxfmt + prettier |
Code formatting | configuration/oxfmt.config.ts, configuration/prettier.config.ts |
eslint + oxlint |
Linting (TS/JS) | project eslint.config.ts, configuration/oxlint.config.ts |
ruff |
Format + lint (Python) | pyproject.toml |
tsc --noEmit |
TypeScript type checking | project tsconfig.json → configuration/tsconfig.base.json |
pyright + ty |
Python type checking | pyproject.toml |
knip |
Unused TS files, exports, deps | configuration/knip.config.ts |
fallow dead-code |
The same, workspace-wide in one pass | configuration/fallow.config.jsonc |
vulture |
Unused Python code | configuration/vulture_whitelist.py |
cspell |
Spell checking | configuration/cspell.config.yaml |
markdownlint |
Markdown linting | configuration/.markdownlint-cli2.jsonc |
yamllint |
YAML linting | configuration/yamllint.yaml |
Validation Workflow
Step 1 — Auto-fix
Run lint-codebase in write mode to automatically fix all auto-fixable issues (formatting, linting, unused-code whitelist entries, sync checks):
pnpm exec nx affected --target=lint-codebase --configuration=write --base=main
For new/untracked files that
nx affectedwon't detect, target the relevant project(s) directly:pnpm exec nx run <project>:lint-codebase --configuration=write
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 · 152 lines · 96 tokens per session scan A 9f5d08eba0a3
validate-code is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,900 once invoked, about $0.0005 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-03.
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…