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 commands/jpoutrin/product-forge/forge-refreshgit 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.00007 | $0.01429 |
| Opus 5 | $0.00003 | $0.00714 |
| Sonnet 5 | $0.00001 | $0.00286 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
forge-refresh 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forge-refresh
Category: Plugin Management
Usage
/forge-refresh [options] [plugin-name]
Options
| Option | Description |
|---|---|
--dry-run |
Preview actions without making changes |
--force |
Force reinstall even if all plugins are up to date |
--status |
Show current cache status only (no changes made) |
--verbose |
Show detailed issue descriptions for each plugin |
[plugin-name] |
Optional: Refresh only specific plugin (e.g., product-design) |
Purpose
Validates Product Forge plugin cache state and refreshes outdated, corrupted, or invalid plugins. Use this command when:
- Claude Code becomes unstable or unresponsive
- Plugins don't appear or respond in Claude Code
- Skills, commands, or agents are not recognized
- After pulling updates to the source repository
- When cache appears to be out of sync with source
How It Works
This command performs six phases of cache management:
- Prerequisites - Verifies claude CLI, git, and jq are available
- Detection - Scans plugin cache and compares with source repository
- Reporting - Shows status of each plugin and any issues found
- Backup - Creates timestamped backup of current installation state
- Reinstallation - Clears stale cache and reinstalls plugins
- Verification - Confirms installations succeeded and match source
What Gets Checked
For each plugin, the command validates:
- SHA Match: Installed version matches source repository commit
- Cache Exists: Plugin cache directory is present
- Plugin Valid: Plugin structure passes validation checks
Status indicators:
- ✅ OK - Plugin is up to date and valid
- ⚠️ OUTDATED - Source has newer commits
- ❌ CORRUPTED - Cache directory missing
- ❌ INVALID - Plugin structure validation failed
- ⭕ MISSING - Plugin not installed at all
Execution Instructions for Claude Code
When this command is run, Claude Code should:
1. Parse the Arguments
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 · 243 lines · 7 tokens per session scan A 45c1d854f023
forge-refresh is a command published in the GitHub repository jpoutrin/product-forge (15 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 1,429 once invoked, about $0.0000 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.