Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/rainsunme/toolcapsule/toolcapsule-release)<a href="https://agentmods.dev/skills/rainsunme/toolcapsule/toolcapsule-release"><img src="https://agentmods.dev/badge/skills/rainsunme/toolcapsule/toolcapsule-release.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.1 | $0.00053 | $0.01899 |
| Opus 5 | $0.00026 | $0.00949 |
| Sonnet 5 | $0.00011 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade C, and why
toolcapsule-release scanned grade C with 2 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 7d 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.
rm -rf /tmp/toolcapsule-final-check Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -I --max-time 20 http://toolcapsule.studio || true How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ToolCapsule Development and Release Workflow
Use this skill for ToolCapsule maintenance, releases, and launch operations.
Project Facts
- Repository:
https://github.com/RainSunMe/toolcapsule - Local path:
/home/yingbo/code/toolcapsule - Package name:
toolcapsule - CLI binaries:
toolcapsuletcap
- Website domain:
https://toolcapsule.studio - Vercel fallback URL:
https://toolcapsule.vercel.app - Vercel project:
toolcapsule - npm package:
https://www.npmjs.com/package/toolcapsule - Current initial published version:
0.1.0-alpha.0 - GitHub Environment for Trusted Publishing:
npm
Core Positioning
ToolCapsule is not merely "MCP as Skill". Use this positioning:
Heavy MCP tools don't belong in your prompt. Put them in a ToolCapsule.
Full description:
ToolCapsule inventories existing MCPs, turns selected heavy servers into lazy Agent Skills, and keeps calls file-first with auditable runs and patch-and-retry recovery.
Keep MCP and Skill prominent in README, website, npm description, topics, and launch copy.
Golden Rules
- Keep this project independent from
mify-prism. - Do not commit secrets,
.env, Vercel local auth files, npm tokens, or private MCP endpoints. - Do not publish the same npm version twice.
- Do not tag a version before
package.jsonhas been bumped and committed. - Always run CI locally before publishing or pushing release changes.
- Keep
tcapas a short alias, but avoidtcbecause it conflicts with Linux traffic control and npmtc. - Use npm Trusted Publishing, not
NPM_TOKEN, unless explicitly changing the release model.
Standard Validation
Run before any push/release:
cd /home/yingbo/code/toolcapsule
corepack pnpm run ci
node dist/cli.js --help
Expected:
- TypeScript check passes.
- ESLint passes.
- Vitest passes.
- tsup build succeeds.
- CLI help prints
toolcapsule/0.1.0-alpha.*.
For npm package validation:
npm pack --dry-run
For installed binary validation after publish:
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.
- 7d ago First seen · 291 lines · 53 tokens per session scan C f00785d1cde5
toolcapsule-release is a skill published in the GitHub repository RainSunMe/toolcapsule (2 stars, last pushed 9d ago), licensed MIT. It adds 53 tokens to every session and 1,899 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.