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/bostonorange/claude-code-framework/validatenpx skills add BostonOrange/claude-code-framework --skill validategit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00034 | $0.01531 |
| Opus 5 | $0.00017 | $0.00766 |
| Sonnet 5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
validate 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate
Validate code against project standards and conventions. Runs all checks and produces a report.
Usage
/validate TICKET-1234 # Validate files for a specific ticket
/validate # Validate all uncommitted changes
Process
- Identify changed files — scope to ticket or all uncommitted changes
- Load domain references — based on what's touched
- Run all checks — see check matrix below
- Output report — checklist with ERROR/WARN/PASSED counts
Identifying Changed Files
Ticket-scoped (ID provided):
git diff --name-only origin/{{BASE_BRANCH}}...HEAD
Filter to files matching the ticket. Also check docs/stories/{TICKET_ID}/.
All uncommitted (no ID):
git diff --name-only HEAD
git diff --name-only --cached
Check Matrix
IMPORTANT: Customize this section for your project. The checks below are templates — replace with your actual coding standards.
Code Standards (ERROR)
| Check | How to Detect | Severity |
|---|---|---|
| Error handling on catch blocks | Grep for catch blocks, verify each has proper error tracking | ERROR |
| No debug/console.log in production | Grep for debug statements in non-test files | ERROR |
| No commented-out code | Grep for patterns of commented code | WARN |
| No hardcoded secrets/IDs | Grep for patterns matching secrets, IDs, tokens | ERROR |
| Test classes/files follow conventions | Check test file naming and structure | ERROR |
| Type conventions | Check language-specific type usage | WARN |
| No queries/IO in loops | Check for performance anti-patterns | ERROR |
| Constants over magic values | Flag repeated string/number literals | WARN |
Test Quality (ERROR)
| Check | How to Detect | Severity |
|---|---|---|
| No inline test data construction | Tests should use factories/fixtures | ERROR |
| No production data in tests | Check for SeeAllData or equivalent |
ERROR |
| Uses test helpers/factories | Verify standard test patterns used | WARN |
| Adequate assertions | Check test methods have assertions | WARN |
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 · 170 lines · 34 tokens per session scan A 256bcfb12db9
validate is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,531 once invoked, about $0.0002 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…