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 skills add deeflect/dory --skill dory-searchgit clone --depth 1 https://github.com/deeflect/doryWrote 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/deeflect/dory/dory-search)<a href="https://agentmods.dev/skills/deeflect/dory/dory-search"><img src="https://agentmods.dev/badge/skills/deeflect/dory/dory-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/deeflect/dory/dory-search"><img src="https://agentmods.dev/badge/skills/deeflect/dory/dory-search.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00381 |
| Opus 5.5 | $0.00014 | $0.00152 |
| Sonnet 5.5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
dory-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 2mo 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
Dory Search
Use dory search before answering factual questions about people, projects, decisions, dates, or prior sessions.
Workflow:
- If the task asks for a fast recent recap, use
dory_digestfirst instead of searching for adigesttag. - Start normal fact retrieval with
uv run dory --corpus-root <corpus> --index-root <index> search "<query>" - If needed, follow with
dory get <path>on the best hit - If a result has
stale_warning, treat it as possibly outdated and look for fresher evidence
Rules:
- Prefer retrieval over guessing
- Use search even if wake seems related; wake is cached context, search is live evidence
- Do not assume digest files have a searchable
digesttag;dory_digestresolvesdigests/daily,digests/weekly, and legacylogs/**paths directly - Use
mode=exactfor cleanup markers, unique strings, and artifact existence checks - Use
mode=text,mode=keyword, ormode=lexicalwhen you want BM25-only search; all three normalize tobm25 - Use
mode=semanticwhen you want vector-only search; it normalizes tovector - Hybrid search is deterministic by default; LLM-assisted planning, expansion, and reranking require explicit
DORY_QUERY_*server flags - Use
rerank="false"for baseline deterministic search,rerank="true"to force the configured reranker, andrerank="auto"to follow server defaults
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.
- 2mo ago First seen · 25 lines · 34 tokens per session scan A b8165ff09532
dory-search is a skill published in the GitHub repository deeflect/dory (13 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 381 once invoked, about $0.0001 per session on Opus 5.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
agentmemory-agents
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
md-fetch-summarize
Fetch a URL and return a concise markdown summary of its content. Read-only: no files are written; the summary is returned as output only. Use when asked to "fetch and summarize", "summarize this URL", "what does this page say", or "get the content of ". Proactively suggest when the user pastes a URL and asks what it…
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.