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/is-bo/fullstack-forge-skill/forge-recoverynpx skills add is-bo/fullstack-forge-skill --skill forge-recoverygit clone --depth 1 https://github.com/is-bo/fullstack-forge-skillWrote 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/is-bo/fullstack-forge-skill/forge-recovery)<a href="https://agentmods.dev/skills/is-bo/fullstack-forge-skill/forge-recovery"><img src="https://agentmods.dev/badge/skills/is-bo/fullstack-forge-skill/forge-recovery.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.00027 | $0.00340 |
| Opus 5 | $0.00014 | $0.00170 |
| Sonnet 5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
forge-recovery 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 4d 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.
What it actually says
Fullstack Forge adapter: forge-recovery
This file is a pointer maintained by Fullstack Forge. It exists so this agent host can discover and trigger the skill. The full playbook is not duplicated here: one canonical copy is shared by every installed host.
Read the canonical playbook now and follow it exactly:
../../../.fullstack-forge/skills/forge-recovery/SKILL.md
That path is relative to this file. From the installation root it is
.fullstack-forge/skills/forge-recovery/SKILL.md. Every resource the playbook references
(fullstack-forge/references/..., fullstack-forge/schemas/...,
fullstack-forge/templates/..., fullstack-forge/profiles/...) resolves relative to
.fullstack-forge/skills/.
The canonical playbook owns any deterministic composition step; perform that step exactly
once. This adapter never adds a second workflow or composition command.
Do not edit this adapter; edit the canonical playbook instead. If the canonical file is
missing or unreadable the installation is damaged. Report it and repair through the same
project-package, archive, or plugin mechanism that installed this adapter. Never fall back to
an unpinned npx forge, which may resolve an unrelated public package.
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.
- 4d ago First seen · 30 lines · 27 tokens per session scan A f92e9c2f2692
forge-recovery is a skill published in the GitHub repository is-bo/fullstack-forge-skill (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 27 tokens to every session and 340 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-31.
Other skills, from other repositories
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
bootstrap-local-dev
Set up a fresh authgear-server development environment from scratch. Use when onboarding a new contributor, setting up a new machine, or when the user says "set up local dev from scratch" / "first-time setup". Covers the asdf + Homebrew install path on macOS; Nix users should follow CONTRIBUTING.md directly.
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
ably-automation
Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.