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 skills add J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill agent-recoverygit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/agent-recovery)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/agent-recovery"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/agent-recovery/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.
<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/agent-recovery"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/agent-recovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 143 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00032 | $0.00864 |
| Opus 5 | $0.00016 | $0.00432 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
agent-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 11d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Recovery Skill
Protocols for when the agent is stuck, context is degraded, or session needs migration.
When to Use
- Agent is making repeated mistakes
- Long conversation causing hallucinations
- Need to hand off to fresh agent
- Context window is full
Option 1: Escalate (Handoff Report)
Use when: Agent is stuck and can't solve the problem.
Steps
- Undo broken changes:
git status
git checkout -- .
- Generate
docs/escalation_report.md:
# Escalation Handoff Report
**Generated:** [Date/Time]
**Original Issue:** [GitHub Issue # or description]
## PART 1: THE DAMAGE REPORT
### 1.1 Original Goal
[The task you were asked to complete]
### 1.2 Observed Failure
[EXACT error message]
### 1.3 Failed Approach
[Strategy you attempted]
### 1.4 Key Files Involved
- `path/to/file1.ts`
### 1.5 Best-Guess Diagnosis
[Why approach failed]
## PART 2: FULL FILE CONTENTS
[EMBED entire content of each file]
## PART 3: DIRECTIVE FOR ORCHESTRATOR
1. Analyze the failure
2. Formulate a new plan
3. Execute or hand off
- Open new session and paste the report content.
Option 2: Migrate (Context Snapshot)
Use when: Chat is stale, need fresh session with same context.
Auto-Detect Context
cat docs/Project_Requirements.md 2>/dev/null
git log --oneline -20
gh issue list --state open --limit 10 --json number,title
cat docs/Coding_Guidelines.md 2>/dev/null
Generate docs/migration_snapshot.md:
# State Snapshot Handoff Prompt
## To the New AI: Adopt This Identity
You are the **VibeCode Project Orchestrator**...
## Project Details
- **Name:** [from PRD]
- **Stack:** [from PRD]
## Milestones
[From git log]
## Current Status
- In Progress: [from GitHub]
- Next: [from roadmap]
## Key Files
- `docs/Project_Requirements.md`
- `docs/Coding_Guidelines.md`
## First Action
Read files above, then ask: "What would you like to work on next?"
Option 3: Reset (Mid-Conversation)
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.
- 11d ago First seen · 150 lines · 32 tokens per session scan A ff981a77f4f2
agent-recovery is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed today), licensed ISC. It adds 32 tokens to every session and 864 once invoked, about $0.0002 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
code-review
Reviews code for bugs, security issues, and best practices.
error-translator
A Chinese-language assistant that translates English programming errors and explains what they mean. It covers common errors from languages and frameworks including Python, JavaScript, TypeScript, Java, and others.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.
perf-profiler
A performance investigation guide that uses repeatable measurements and profiling evidence to find where software spends time or resources. Profiling records runtime activity such as CPU use, memory use, database work, or network delays.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
bug-reproducer
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix. Also turn bug reports, stack traces, screenshots, failing behavior, support tickets, and regressions into minimal reproducible cases with red-to-green evidence. Use when…