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 commands/davidsmorais/mcpocket/releasegit clone --depth 1 https://github.com/davidsmorais/mcpocketWhat 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.00020 | $0.00306 |
| Opus 5 | $0.00010 | $0.00153 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
release 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 2d 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
Commit all current changes, push to GitHub, bump the patch version in package.json, update CHANGELOG.md with the new version, and publish to the npm registry.
Follow these steps in order:
-
Commit & Push:
- Stage all modified files (exclude
.claude/settings.local.jsonand other local/session files) - Use
git addthengit commitwith a concise message describing the changes - Push to the remote with
git push
- Stage all modified files (exclude
-
Bump Version:
- Read the current version from
package.json - Increment the patch version (e.g.,
0.6.6→0.6.7) - Update
package.jsonwith the new version
- Read the current version from
-
Update Changelog:
- Read
CHANGELOG.md - Insert a new version entry at the top (after the header) with today's date
- Summarize the changes from the commit message
- Read
-
Publish to npm:
- Run
npm publish(orpnpm publishif the project uses pnpm) - Verify the publish succeeded
- Run
-
Verify:
- Run
git statusto confirm working tree is clean - Run
git log -3 --onelineto show the new commit
- 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.
- 2d ago First seen · 32 lines · 20 tokens per session scan A 43b7449a6dcd
release is a command published in the GitHub repository davidsmorais/mcpocket (9 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 306 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.