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 copy-skillgit 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/copy-skill)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/copy-skill"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/copy-skill/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/copy-skill"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/copy-skill.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.00015 | $0.00978 |
| Opus 5.5 | $0.00006 | $0.00391 |
| Sonnet 5.5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
copy-skill 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Skill
Copy a skill from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
Usage
# List available skills
/copy-skill
# Copy to project (default)
/copy-skill product-design:python-style
# Copy to user level
/copy-skill product-design:python-style --user
# Explicit project level
/copy-skill git-workflow:commit-patterns --project
Arguments
<plugin>:<skill-name>- The skill to copy inplugin:nameformat--user- Copy to~/.claude/{plugin}/skills/{name}/--project- Copy to.claude/{plugin}/skills/{name}/(default)
What Gets Copied
Skills are copied as entire directories, including:
SKILL.md- The main skill definition- Any additional files (scripts/, references/, *.yaml, etc.)
Example: parallel-agents skill contains both SKILL.md and agent-skills-mapping.yaml.
Directory Structure
# Project-level (default)
.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.md
# User-level (--user)
~/.claude/
└── product-design/
└── skills/
└── python-style/
└── SKILL.md
Execution Instructions
When the user runs this command:
No Arguments - List Available Skills
-
Scan Product Forge plugins cache for all available skills:
ls ~/.claude/plugins/cache/product-forge-marketplace/*/skills/ 2>/dev/null -
For each plugin with skills, list them with descriptions:
- Read
SKILL.mdfrontmatter to getnameanddescription - Format as:
{plugin}:{skill-name} - {description}
- Read
-
Display formatted list:
Available skills from Product Forge: product-design: python-style - Python coding style and PEP standards prd-management - Automatic PRD lifecycle management parallel-agents - Multi-agent orchestration patterns ... git-workflow: commit-patterns - Git commit best practices ... Usage: /copy-skill <plugin>:<skill-name> [--user | --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 · 148 lines · 15 tokens per session scan A f2849e7d83d2
copy-skill is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 978 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…