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/cavinooo/claude-find/findnpx skills add Cavinooo/claude-find --skill findgit clone --depth 1 https://github.com/Cavinooo/claude-findWrote 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/cavinooo/claude-find/find)<a href="https://agentmods.dev/skills/cavinooo/claude-find/find"><img src="https://agentmods.dev/badge/skills/cavinooo/claude-find/find.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.00027 | $0.00206 |
| Opus 5 | $0.00014 | $0.00103 |
| Sonnet 5 | $0.00005 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
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 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
Use the search_sessions MCP tool (from the claude-find server) to search past Claude Code sessions.
Pass the user's query to the tool. If the user said /find auth discussion, use "auth discussion" as the query.
Scope rules:
- Default: search only the current project (
scope: "current") - If user says "across all projects" or "in all projects": use
scope: "all" - If user mentions a specific project name: use
project_filterwith that name
After receiving results, synthesize the key context for the user — including reasoning, decisions, failed approaches, and constraints from the past session. Present it as useful context for the current conversation.
If no results are found, suggest trying scope: "all" to search across all projects, or different search terms.
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 · 18 lines · 27 tokens per session scan A bb44d6fb5296
find is a skill published in the GitHub repository Cavinooo/claude-find (11 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 206 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-30.
Other skills, from other repositories
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
weknora-rag-search
Use when retrieving from or asking questions against a WeKnora knowledge base via the weknora CLI — and especially when unsure whether to use chat, session ask, or search chunks for a given goal.
wiki_guide
Guidance for the Obsidian-compatible wiki vault.
uteke-memory
Persistent memory engine for AI agents via the uteke CLI — remember, recall, search, forget with semantic + FTS5 hybrid search, documents, knowledge graph, rooms, tiered memory, and multi-agent namespaces.
memory-processor
Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…