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/copy-agentnpx skills add jpoutrin/product-forge --skill copy-agentgit 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-agent)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/copy-agent"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/copy-agent.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.00014 | $0.01028 |
| Opus 5 | $0.00007 | $0.00514 |
| Sonnet 5 | $0.00003 | $0.00206 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
copy-agent 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Agent
Copy an agent from Product Forge plugins to your user-level (~/.claude/) or project-level (.claude/) directory.
Usage
# List available agents
/copy-agent
# Copy to project (default)
/copy-agent product-design:product-architect
# Copy to user level
/copy-agent git-workflow:commit-expert --user
# Explicit project level
/copy-agent python-experts:django-expert --project
Arguments
<plugin>:<agent-name>- The agent to copy inplugin:nameformat--user- Copy to~/.claude/{plugin}/agents/{name}.md--project- Copy to.claude/{plugin}/agents/{name}.md(default)
What Gets Copied
Agents are single markdown files (.md) containing:
- YAML frontmatter with name, description, tools, model, and color
- Agent capabilities and activation triggers
- Autonomous workflow definitions
Directory Structure
# Project-level (default)
.claude/
└── git-workflow/
└── agents/
└── commit-expert.md
# User-level (--user)
~/.claude/
└── git-workflow/
└── agents/
└── commit-expert.md
Execution Instructions
When the user runs this command:
No Arguments - List Available Agents
-
Scan Product Forge plugins cache for all available agents:
ls ~/.claude/plugins/cache/product-forge-marketplace/*/agents/*.md 2>/dev/null -
For each plugin with agents, list them with descriptions:
- Read agent file frontmatter to get
name,description, andmodel - Format as:
{plugin}:{agent-name} ({model}) - {description}
- Read agent file frontmatter to get
-
Display formatted list:
Available agents from Product Forge: product-design: product-architect (sonnet) - Full product development guidance prd-orchestrator (sonnet) - PRD lifecycle management qa-tester (sonnet) - Manual QA test procedure creation web-debugger (sonnet) - Web application debugging ... git-workflow: commit-expert (haiku) - Git commit specialist rebase-expert (haiku) - Git rebase specialist code-review-expert (sonnet) - Code review orchestrator ... python-experts: django-expert (sonnet) - Django web application specialist fastapi-expert (sonnet) - FastAPI async REST API specialist ... Usage: /copy-agent <plugin>:<agent-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.
- 5d ago First seen · 149 lines · 14 tokens per session scan A f0bd1959ff9a
copy-agent is a skill published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,028 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…