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/penwyp/claudepreference/develop-review-gatenpx skills add penwyp/ClaudePreference --skill develop-review-gategit clone --depth 1 https://github.com/penwyp/ClaudePreferenceWhat 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.00108 | $0.00750 |
| Opus 5 | $0.00054 | $0.00375 |
| Sonnet 5 | $0.00022 | $0.00150 |
| Haiku 4.5 | $0.00011 | $0.00075 |
Grade A, and why
develop-review-gate 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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Review Gate
Workflow
- Confirm scope and current workspace state.
- Work in the current checkout instead of creating a worktree.
- Inspect the repository and any existing local changes before editing.
- If the worktree is already dirty, preserve unrelated user changes and limit edits to the task scope.
- Implement the requested change in the current checkout.
- Explore the relevant code before editing.
- Finish the feasible scope instead of stopping at a partial patch.
- Keep architecture consistent with the project; do not use temporary patch-style fixes unless the change is truly a local no-risk micro-fix.
- Run self-review pass 1.
- Inspect the diff as a reviewer instead of as the original author.
- Look for correctness bugs, regressions, missing tests, naming issues, leaky abstractions, and unnecessary complexity.
- Apply the fixes that are clearly actionable.
- Run the most relevant tests, lint, or build checks for the changed area.
- Run self-review pass 2.
- Re-inspect the updated diff with the same reviewer mindset.
- Focus on issues left after the first pass: edge cases, maintainability, API consistency, error handling, and test quality.
- Apply the second-pass fixes that materially improve the result.
- Re-run the most relevant verification after the refactor.
- Produce the approval gate output and pause.
- Report the final review findings first. If no blocking findings remain, say that explicitly.
- Summarize what changed, what was refactored during both self-review passes, what verification ran, and what did not run.
- Include the current branch, touched files, and working tree status when relevant.
- Call out residual risks or open questions.
- End in a waiting state such as:
Awaiting human confirmation: continue coding, request more changes, commit, or proceed with the next step. - Do not continue into extra scope, commit, or destructive cleanup unless the human explicitly confirms.
Review Output
Use concise sections in this order:
Self-review findingsChange summaryRefactors appliedVerificationResidual risksAwaiting confirmation
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 73 lines · 108 tokens per session scan A 609c5a660df8
develop-review-gate is a skill published in the GitHub repository penwyp/ClaudePreference (137 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 750 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-08-30.
Other skills, from other repositories
nemoclaw-contributor-implement-issue
Implement an accepted NemoClaw GitHub issue in the current checkout. Use when a user asks to pick up an issue for implementation, implement or fix a named issue, or add the issue's tests. Confirm accepted scope, deliver the smallest independently valuable capability slice, and record validation and remaining gates…
amazon-bestseller-listing
Amazon Best Sellers listing scraper: extract product cards from any Amazon Best Sellers (zgbs) or /gp/bestsellers/ category page — returns rank (position on chart), asin, title, url, image, imageAlt, price, stars, reviewCount, ratingRaw per item, plus category metadata (categoryName, categoryFullName, categoryUrl) and…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
cabloy-worktree-environment
This skill must be used only when the user explicitly invokes /cabloy-worktree-environment or explicitly asks to perform the named Cabloy worktree-environment setup. It prepares a confirmation-gated, worktree-local Vona and Zova runtime environment for a linked Cabloy Basic or Cabloy Start Git worktree using Git…
shopify-hydrogen
Hydrogen storefront implementation cookbooks. Some of the available recipes are: B2B Commerce, Bundles, Combined Listings, Custom Cart Method, Dynamic Content with Metaobjects, Express Server, Google Tag Manager Integration, Infinite Scroll, Legacy Customer Account Flow, Markets, Partytown + Google Tag Manager…