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/integrate-commandnpx skills add jpoutrin/product-forge --skill integrate-commandgit clone --depth 1 https://github.com/jpoutrin/product-forgeWhat 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.00926 |
| Opus 5 | $0.00007 | $0.00463 |
| Sonnet 5 | $0.00003 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
integrate-command 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Command
Import a command from your user-level (~/.claude/) or project-level (.claude/) directory into a Product Forge plugin.
Usage
# Integrate from user level (default source)
/integrate-command my-command --plugin=claude-code-dev
# Integrate from project level
/integrate-command my-command --plugin=claude-code-dev --source=project
# Integrate from a specific plugin subdirectory
/integrate-command my-command --plugin=git-workflow --source=user
Arguments
<command-name>- Name of the command to integrate (without .md extension)--plugin=<name>- Target Product Forge plugin (required)--source=user|project- Where to find the command (default:user)
Source Locations
--source=user: Searches in~/.claude/*/commands/directories--source=project: Searches in.claude/*/commands/directories
Execution Instructions
When the user runs this command:
1. Parse Arguments
- Extract
command-namefrom first argument - Extract
pluginfrom--plugin=flag (required) - Extract
sourcefrom--source=flag (default:user)
2. Locate Source Command
Search for the command file:
# For --source=user
find ~/.claude -path "*/commands/${command-name}.md" -type f 2>/dev/null
# For --source=project
find .claude -path "*/commands/${command-name}.md" -type f 2>/dev/null
If multiple matches found, list them and ask user to specify the full path.
If not found:
Command '${command-name}' not found in ${source} level.
Searched locations:
- ~/.claude/*/commands/${command-name}.md
Available commands:
[list available .md files in commands directories]
3. Validate Target Plugin
Check the target plugin exists in Product Forge:
ls plugins/${plugin}/.claude-plugin/plugin.json
If not found:
Plugin '${plugin}' not found in Product Forge.
Available plugins:
- claude-code-dev
- product-design
- git-workflow
- python-experts
- ...
4. Determine Destination
DESTINATION=plugins/${plugin}/commands/${command-name}.md
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 · 153 lines · 14 tokens per session scan A 99425aa928b0
integrate-command 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 926 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
agent-messaging
Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…