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/seongjaeryu/bindly-claude-code/searchnpx skills add seongjaeryu/bindly-claude-code --skill searchgit clone --depth 1 https://github.com/seongjaeryu/bindly-claude-codeWrote 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/seongjaeryu/bindly-claude-code/search)<a href="https://agentmods.dev/skills/seongjaeryu/bindly-claude-code/search"><img src="https://agentmods.dev/badge/skills/seongjaeryu/bindly-claude-code/search.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.00006 | $0.00352 |
| Opus 5 | $0.00003 | $0.00176 |
| Sonnet 5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
search 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 5d 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
Search the user's Bindly knowledge base for relevant context.
Purpose
Help users find and retrieve knowledge they've previously saved to Bindly. This searches your account at bindly.app, not local files or conversation history.
Workflow
When the user wants to search their knowledge:
-
Understand Intent: Clarify what the user is looking for
- A specific topic or concept?
- Related to a project or domain?
- Recent activity or older knowledge?
-
Search: Use
mcp_searchwith appropriate query- Semantic search works across all Spaces
- Can filter by Space if needed
-
Present Results (Tier 1): Show summaries first
- Title and key points
- Entities and tags
- Creation/update date
- This saves tokens and gives quick overview
-
Deep Dive (Tier 2): On request, retrieve full content
- Use
mcp_get_bindingwith tier=2 - Show complete source content
- Offer version history if relevant
- Use
-
Suggest Related: Help exploration
- Point out related bindings
- Suggest Sets that might be relevant
- Offer to organize findings
Example Prompts
- "What do I know about authentication patterns?"
- "Find my notes on React performance"
- "Search for anything related to API design"
Key Points
- Searches bindly.app, not local storage
- Two-tier retrieval: summaries first, full content on demand
- Can search across all Spaces or filter to specific ones
- Results are the same as what you'd see in other connected agents
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.
- 5d ago First seen · 53 lines · 6 tokens per session scan A b877787eefde
search is a skill published in the GitHub repository seongjaeryu/bindly-claude-code (8 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 352 once invoked, about $0.0000 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
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
setup
Scaffold a complete knowledge system. Detects platform, conducts conversation, derives configuration, generates everything. Validates against 15 kernel primitives. Triggers on "/setup", "/setup --advanced", "set up my knowledge system", "create my vault".
cortex-broadcast
Propagate insights from a distilled Raw into related existing Notes/Projects pages through conversational per-page edits.
cortex-distill
Distill raw session records into refined Notes and Projects. Use when the user says "提煉", "整理 raw", "distill", or "distill raw records".
reduce
Extract structured knowledge from source material. Comprehensive extraction is the default — every insight that serves the domain gets extracted. For domain-relevant sources, skip rate must be below 10%. Zero extraction from a domain-relevant source is a BUG. Triggers on "/reduce", "/reduce [file]", "extract…
cortex-query
Search and retrieve content from the cortexes vault — the user's external memory. Use when the user explicitly asks to search or recall the vault ("查 cortex", "之前有記過", "cortex 裡有沒有", "check my notes", "what did I write about", /cortexes:query), or when the using-cortex skill routes a request here after one of its four…