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/afk-surf/openbridge/skill-managernpx skills add AFK-surf/OpenBridge --skill skill-managergit clone --depth 1 https://github.com/AFK-surf/OpenBridgeWrote 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/afk-surf/openbridge/skill-manager)<a href="https://agentmods.dev/skills/afk-surf/openbridge/skill-manager"><img src="https://agentmods.dev/badge/skills/afk-surf/openbridge/skill-manager.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.00066 | $0.00688 |
| Opus 5 | $0.00033 | $0.00344 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade C, and why
skill-manager scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
3. **Delete**: `rm -rf ~/.openbridge/skills/custom/<skill-slug>/` How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Manager
This skill provides guidance for all skill-related operations: creating, installing, modifying, and deleting skills.
About Skills
Skills are modular, self-contained packages that extend the agent by providing specialized workflows and bundled resources. Think of them as an "onboarding guide" for a specific task category.
Skill Directories
User skills live under ~/.openbridge/skills/:
| Directory | Purpose |
|---|---|
custom/ |
User-created skills |
imported/ |
Skills imported from the OpenBridge skill library |
Synced local skills may also appear through configured sync folders. Those stay at their original locations and are not installed into ~/.openbridge/skills/.
IMPORTANT: When creating or installing managed local skills, always use ~/.openbridge/skills/custom/<skill-slug>/ unless the flow explicitly targets imported/.
Operation: Install Skill from URL
When the user provides a URL to a skill (e.g., https://example.com/dot_claude/skills/xxx/SKILL.md) and asks to "install this skill".
Read the detailed guide: references/install-from-url.md
Operation: Install Skill via npx skills CLI
When the user asks to install a skill using npx skills add.
Read the detailed guide: references/install-from-npx-skills.md
Operation: Create Skill from Current Conversation
Convert the current multi-turn chat solution into a reusable custom skill.
Read the detailed guide: references/create-from-conversation.md
Operation: Modify Existing Skill
When the user asks to modify, edit, or update an existing skill:
- Locate the SKILL.md in
~/.openbridge/skills/(check custom/ and imported/) or in a configured sync folder - Read current content
- Apply changes as requested
- Validate if possible
- Report what was changed
Note: System skills are read-only. To customize behavior, create a new skill under ~/.openbridge/skills/custom/.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 86 lines · 66 tokens per session scan C c9adfe941518
skill-manager is a skill published in the GitHub repository AFK-surf/OpenBridge (426 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 688 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…