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/ramakrishnan24689/codeapps-toolkit/build-lint-validatornpx skills add Ramakrishnan24689/codeapps-toolkit --skill build-lint-validatorgit clone --depth 1 https://github.com/Ramakrishnan24689/codeapps-toolkitWhat 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.00027 | $0.02106 |
| Opus 5 | $0.00014 | $0.01053 |
| Sonnet 5 | $0.00005 | $0.00421 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
build-lint-validator 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 3d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build & Lint Validator Skill
Purpose
Systematically validate that implemented code compiles successfully and passes ESLint rules before delivery. This skill acts as the final quality gate to catch compilation errors, type issues, and linting violations that would otherwise be discovered by the user during their own build process.
When to Use This Skill
ALWAYS use after:
- Completing feature implementation (Phase 3 of implementation workflow)
- Making significant code changes across multiple files
- Before creating pull requests or commits
- Before marking implementation tasks as complete
Use to validate:
- TypeScript compilation success (no type errors)
- ESLint rule compliance (no linting violations)
- Build process completeness (all dependencies resolved)
- Code quality standards adherence
Validation Framework
This skill performs 3 critical checks:
1. TypeScript Compilation Check
Ensures all TypeScript code compiles without errors.
2. ESLint Compliance Check
Verifies code passes all ESLint rules and style guidelines.
3. Auto-Fix Capability
Attempts to automatically fix common linting issues when possible.
Validation Process
Step 1: Run TypeScript Compilation
Execute the build command to check for compilation errors:
npm run build
What to check:
- Build exits with code 0 (success)
- No TypeScript compilation errors
- No missing dependencies
- All imports resolve correctly
- All type definitions valid
Common TypeScript errors:
- Type mismatches (e.g.,
Type 'string' is not assignable to type 'number') - Missing imports (e.g.,
Cannot find module '@/components/Button') - Undefined properties (e.g.,
Property 'foo' does not exist on type 'Bar') - Generic type errors (e.g.,
Type 'X' does not satisfy the constraint 'Y')
Step 2: Run ESLint Check
Execute the lint command to check for style violations:
npm run lint
What to check:
- Lint exits with code 0 (success)
- No ESLint errors
- No ESLint warnings (if strict mode)
- All files pass configured rules
- No unused imports or variables
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.
- 3d ago First seen · 310 lines · 27 tokens per session scan A 80c1dfca1aae
build-lint-validator is a skill published in the GitHub repository Ramakrishnan24689/codeapps-toolkit (6 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 2,106 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-31.
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…