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 skills add jpoutrin/product-forge --skill pattern-detectiongit clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/pattern-detection)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/pattern-detection"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/pattern-detection/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/pattern-detection"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/pattern-detection.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.01146 |
| Opus 5.5 | $0.00013 | $0.00458 |
| Sonnet 5.5 | $0.00007 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
pattern-detection 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 1mo 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pattern Detection Skill
Recognize and note reusable patterns during implementation for potential contribution to Product Forge.
Purpose
When working on projects, Claude often implements patterns that could benefit the broader Product Forge ecosystem. This skill helps identify those patterns so they can be captured by the feedback hooks and potentially become new skills, commands, or templates.
Pattern Categories
Code Patterns
Implementations that follow consistent, reusable structures:
- Factory patterns - Test fixtures, mock builders, data generators
- Service layer patterns - Repository, command, query separation
- Error handling - Consistent error types, recovery strategies
- API patterns - Response formatting, pagination, filtering
- Testing patterns - Fixtures, assertions, mocking strategies
Workflow Patterns
Multi-step processes that could be automated:
- Project setup - Directory structures, config files, initial scaffolding
- Code review - Checklists, validation steps, quality gates
- Deployment - Build, test, deploy sequences
- Documentation - Auto-generation, formatting, templates
Configuration Patterns
Settings and configurations that are commonly needed:
- Tool configurations - Linter rules, formatters, CI/CD
- Environment setup - Development, staging, production
- Integration patterns - API keys, service connections
Recognition Triggers
Note patterns when you observe:
- Repetition: Same structure implemented 3+ times
- Best practice: Industry-standard patterns being applied
- Automation opportunity: Manual process that could be scripted
- Convention enforcement: Rules applied manually that could be automated
- Boilerplate reduction: Repeated code that could be templated
Quality Criteria
Only patterns worth capturing should be:
| Criterion | Description |
|---|---|
| Reusable | Applies to multiple projects or contexts |
| Non-trivial | More than simple one-liners or obvious code |
| Generalizable | Not too specific to one codebase |
| Documented | Can be explained clearly to others |
| Tested | Validated in at least one real project |
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.
- 1mo ago First seen · 164 lines · 33 tokens per session scan A 31bc81ff5c74
pattern-detection is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 1,146 once invoked, about $0.0001 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…