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/jpoutrin/product-forge/propose-forge-improvementnpx skills add jpoutrin/product-forge --skill propose-forge-improvementgit 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/propose-forge-improvement)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/propose-forge-improvement"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/propose-forge-improvement.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.1 | $0.00016 | $0.01486 |
| Opus 5 | $0.00008 | $0.00743 |
| Sonnet 5 | $0.00003 | $0.00297 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade B, and why
propose-forge-improvement scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find ~/.claude/plugins/cache -name "*.md" | xargs grep -l "{component-name}" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Propose Forge Improvement
Retrospect on the current session and propose improvements to Product Forge - either enhancing existing components or suggesting new ones.
Purpose
After working with Product Forge skills, commands, or agents, identify opportunities to improve the ecosystem based on real usage patterns.
Usage
/propose-forge-improvement # Analyze and propose improvements
/propose-forge-improvement --save # Save proposal to ~/.claude/learnings/
Decision Flow
Analyze session for Product Forge opportunities
↓
┌─────────────────────────────────────────────┐
│ Could an existing component be improved? │
│ │
│ Check: │
│ - Skills used → Missing guidance? │
│ - Commands run → Missing options? │
│ - Agents spawned → Missing capabilities? │
│ - Docs referenced → Outdated/incomplete? │
└─────────────────────────────────────────────┘
↓
┌─────────┴─────────┐
↓ ↓
Improvement New Component
to existing proposal
Execution Instructions
When the user runs this command:
1. Identify Product Forge Usage
Scan the session for:
- Skills referenced - Which skills were applied or mentioned?
- Commands executed - Which /commands were run?
- Agents spawned - Which Task agents were used?
- Patterns observed - Reusable workflows or code structures?
- Friction points - Where did existing tools fall short?
2. Check for Improvement Opportunities
For each identified component, ask:
| Question | If Yes → |
|---|---|
| Missing guidance in a skill? | Skill improvement |
| Missing option in a command? | Command improvement |
| Missing capability in an agent? | Agent improvement |
| Outdated information in docs? | Doc improvement |
| Workflow that could be automated? | New command |
| Knowledge that should be applied automatically? | New skill |
| Complex task needing specialized agent? | New agent |
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.
- 6d ago First seen · 247 lines · 16 tokens per session scan B af4fa40b764a
propose-forge-improvement is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 1,486 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…