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/ryanjmichie-git/forgeproof-plugin/resetnpx skills add ryanjmichie-git/forgeproof-plugin --skill resetgit clone --depth 1 https://github.com/ryanjmichie-git/forgeproof-pluginWhat 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.00066 | $0.00543 |
| Opus 5 | $0.00033 | $0.00271 |
| Sonnet 5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
reset 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 yesterday.
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.
What it actually says
ForgeProof Reset: Clean Up Local State
Remove ForgeProof artifacts and optionally delete branches for a fresh run.
The provenance engine script is at ${CLAUDE_PLUGIN_ROOT}/skills/run/scripts/forgeproof.py
(referenced as $FP below). Determine the Python interpreter once: run
python3 --version; if that fails or reports Python is not found, use
python. Set $FP_PY to whichever succeeded. The examples use bash syntax;
if your shell is PowerShell, adapt the invocation (& $FP_PY $FP ...).
Step 1 — Determine scope
If $ARGUMENTS contains an issue number, set $ISSUE to that number.
If $ARGUMENTS is --all or empty, clean up all ForgeProof state.
Step 2 — Clean up provenance state
For a single issue:
"$FP_PY" "$FP" reset --issue $ISSUE
For all issues:
"$FP_PY" "$FP" reset --all
Step 3 — Clean up git branches
Check if currently on a forgeproof branch:
git branch --show-current
If on a forgeproof/* branch, switch to main first:
git checkout main
For a single issue, check for the local branch:
git branch --list forgeproof/$ISSUE
If it exists, delete it:
git branch -D forgeproof/$ISSUE
For all issues, list all forgeproof branches:
git branch --list 'forgeproof/*'
Delete each one.
Step 4 — Optionally clean up remote branches
Ask the user if they also want to delete remote branches.
If yes, for a single issue:
git push origin --delete forgeproof/$ISSUE
For all issues, delete each remote forgeproof branch.
Step 5 — Report
Report what was cleaned up: files deleted, branches removed. Confirm the
workspace is ready for a fresh /forgeproof:run run.
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.
- yesterday First seen · 84 lines · 66 tokens per session scan A 3c6d30457465
reset is a skill published in the GitHub repository ryanjmichie-git/forgeproof-plugin (2 stars, last pushed 11d ago), licensed MIT. It adds 66 tokens to every session and 543 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…