integrate-command

integrate-command is a skill for Claude Code from jpoutrin/product-forge. It costs 14 tokens per session (926 once invoked), scanned A, original, MIT.

A command for copying an existing Claude Code command into a Product Forge plugin. It can search either your personal Claude configuration or the current project’s configuration.

In plain words
What is it for?
Use it to import a named command into a selected Product Forge plugin from user-level or project-level command folders.
Why use it?
It avoids manually finding, copying, and placing command files in the plugin’s expected location.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions .claude-plugin; names the AskUserQuestion tool.

Part of the claude-code-dev plugin — 17 skills, 2 hooks shipped together

Good fit Use it to import a named command into a selected Product Forge plugin from user-level or project-level command folders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/integrate-command
Install

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.

Any agent
npx skills add jpoutrin/product-forge --skill integrate-command
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install claude-code-dev, the plugin that ships this one along with the rest of its 17 skills, 2 hooks.

Wrote 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.

agentmods badge for integrate-command

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/integrate-command/github.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/integrate-command)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/integrate-command"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/integrate-command/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.

agentmods 80×15 button for integrate-command

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/integrate-command"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/integrate-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 926 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00926
Opus 5.5 $0.00006 $0.00370
Sonnet 5.5 $0.00003 $0.00185
Haiku 4.5 $0.00001 $0.00093

Measured 1mo ago against content hash 99425aa928b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/claude-code-dev/skills/integrate-command/SKILL.md · 153 lines

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-name from first argument
  • Extract plugin from --plugin= flag (required)
  • Extract source from --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

Read the full file on GitHub · 153 lines

Changes

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.

  1. 1mo ago First seen · 153 lines · 14 tokens per session scan A 99425aa928b0

Subscribe to this mod's changes

integrate-command is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 926 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.

Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 123 tokens