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/sergei-aronsen/claude-code-toolkit/lookupgit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote 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/commands/sergei-aronsen/claude-code-toolkit/lookup)<a href="https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/lookup"><img src="https://agentmods.dev/badge/commands/sergei-aronsen/claude-code-toolkit/lookup.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.00000 | $0.00524 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
lookup 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 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.
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
/lookup — Fast Web Search via Perplexity Pro
Purpose
Quick web search with synthesized answer and citations through your
Perplexity Pro subscription. Runs in search mode (Sonar) — single-pass,
fewer sources, much faster than /research.
Use for "what's the current X" type questions where you need an answer plus a couple of sources, not a deep multi-step investigation.
Usage
/lookup <query>
Examples:
/lookup current Node.js LTS version/lookup Stripe API version as of May 2026/lookup React 19 release date/lookup latest Tailwind CSS v4 breaking changes
When to Use
- Single fact, version, or short answer needed
- Speed matters (~15-20s vs ~90s for
/research) - 5-15 sources is enough
Use /research instead when:
- Need deep multi-step exploration
- Comparing 3+ alternatives
- Need 15+ sources for an audit / draft
Use /factcheck instead when:
- You have a specific claim to verify, not an open question
Pre-flight Checks
Same as /research. See that command for details. Falls back to WebSearch
and context7 if comet-bridge MCP is not available.
Process
- Call
mcp__comet-bridge__comet_connect. - Call
mcp__comet-bridge__comet_askwith:prompt: the user's querymode:searchtimeout:30000(30 seconds)
- Format the response as a short answer + sources list.
Output Format
**Answer:** <one-paragraph synthesized answer>
**Sources:**
- [<title>](<url>)
- [<title>](<url>)
Aim for 1-3 sentences in the answer. If the underlying response is longer, keep the full text but lead with a one-line summary.
Cost & Privacy
- No API tokens spent. See
/researchfor the full Cost & Privacy section. - Queries land in your Perplexity chat history.
Related
/research— deep research with 15-30 sources/factcheck— single-claim verificationcomponents/comet-research.md— security model
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 · 92 lines · 0 tokens per session scan A c010d9b838f3
lookup is a command published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 524 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.