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/jl-cmd/claude-dev-env/reviewsnpx skills add jl-cmd/claude-dev-env --skill reviewsgit clone --depth 1 https://github.com/jl-cmd/claude-dev-envWrote 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/jl-cmd/claude-dev-env/reviews)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/reviews"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/reviews.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.00034 | $0.00722 |
| Opus 5 | $0.00017 | $0.00361 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
reviews 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Guide
Use this guide to evaluate a pull request or code change. Apply the repository's
the repository's checked-in review contract and CODE_RULES.md as its project-specific quality rubric.
Review Judgment
Review work supports code health. Frame each conclusion around observable behavior, maintainability, risk, and the change's intended outcome.
- Use technical evidence and repository conventions to resolve trade-offs.
- Mark a required change when it materially affects correctness, security, reliability, data integrity, maintainability, or the stated behavior.
- Mark optional improvement as
ConsiderorNitso the author can prioritize the work accurately. - Accept an evidence-backed explanation when it satisfies the applicable quality rubric.
Evaluation Criteria
Evaluate the changed code and the surrounding context for:
- Design fit, interfaces, complexity, and future maintenance cost.
- Functional behavior, user impact, edge cases, concurrency, privacy, security, and accessibility where applicable.
- Tests that exercise the changed behavior and distinguish regressions.
- Names, comments, documentation, and style against the repository rubric and the applicable language guide.
- Migration, configuration, compatibility, and operational effects.
Review Workflow
- Read the pull request description and identify the intended outcome.
- Inspect the changed code, relevant callers, and the surrounding design.
- Run or assess relevant verification and identify its coverage boundaries.
- Write each finding with the affected location, observed effect, expected outcome, and supporting evidence.
- State the reviewed scope, verification performed, and any remaining uncertainty in the review output.
Use the comment guide for finding wording and the description guide for description content.
Execution Support
Use available runners for inspection, verification, and repository navigation. This guide supplies the judgment criteria and the corresponding guide anchors.
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.
- 5d ago First seen · 86 lines · 34 tokens per session scan A 9e62a55ad603
reviews is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 722 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…