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/jeanfbrito/rocket-cli/rocket-findnpx skills add jeanfbrito/rocket-cli --skill rocket-findgit clone --depth 1 https://github.com/jeanfbrito/rocket-cliWhat 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.00119 | $0.00847 |
| Opus 5 | $0.00060 | $0.00424 |
| Sonnet 5 | $0.00024 | $0.00169 |
| Haiku 4.5 | $0.00012 | $0.00085 |
Grade A, and why
rocket-find 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 yesterday.
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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rocket-find
Locate a known-ish message across rooms. Local full-text first; server fallback only when scoped to a room.
Transport
- Prefer MCP when connected:
search_messages, thenget_message_contextto expand a hit. - Otherwise shell out:
rocket-cli search <query> --json(add--room <room>to scope),rocket-cli context <messageId> --json. - Multi-server:
--profile <name>(CLI) orROCKET_CLI_PROFILE(MCP env).
Search semantics (FTS5 — important)
- Query terms are split on whitespace and ANDed together — every term must appear. Fewer, more distinctive terms beat a long phrase.
- A trailing
*on a term is a prefix match (deploy*matches deploy/deployed/deployment). Use it when the user gives a stem. - Operators like
AND/OR/NOT/NEARand punctuation are treated as literal text, not syntax — you can't compose boolean queries; pick good terms instead. - Cross-room search is local-only. Without a
room, search runs purely over the local FTS cache across ALL cached rooms (instant, no network). The server fallback (which reaches uncached history) fires ONLY when you pass aroomAND local hits are thin.
Workflow
- Run a cross-room search first.
search_messagesparams:query(required),room(optional),author(optional username filter),limit(1-100, default 20). Start withoutroomso all cached rooms are covered. Choose 1-3 distinctive terms from the user's ask; add a trailing*to stems. - Read the result envelope. It carries each hit's
snippetand asource(localorserver), pluslocalOnlyand an optionalnoteexplaining thin or degraded results. - If hits are thin AND the user implies a room, re-run scoped to that room (
room: "#whatever") to engage the server-side fallback that reaches uncached history. If the user gave no room hint and results are thin, tell them cross-room search is cache-only and offer to scope to a likely room (which enables server search there). - Use
authorwhen the user says "who said X" or "find what posted about Y" — filter by their username. - Present hits ranked, each with: room, author, the snippet, and the permalink. Keep it scannable.
- Offer to expand. "Want the conversation around that one?" →
get_message_context(params:messageId— a hit's id or a pasted link;before0-50 default 10;after0-50 default 5). A thread reply pivots to its whole thread automatically.
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.
- yesterday First seen · 38 lines · 119 tokens per session scan A f912e54cfb7e
rocket-find is a skill published in the GitHub repository jeanfbrito/rocket-cli (2 stars, last pushed 15d ago), licensed MIT. It adds 119 tokens to every session and 847 once invoked, about $0.0006 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
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.