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/thewinci/mimirs/researchnpx skills add TheWinci/mimirs --skill researchgit clone --depth 1 https://github.com/TheWinci/mimirsWrote 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/thewinci/mimirs/research)<a href="https://agentmods.dev/skills/thewinci/mimirs/research"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/research.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.1 | $0.00088 | $0.00491 |
| Opus 5 | $0.00044 | $0.00246 |
| Sonnet 5 | $0.00018 | $0.00098 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
research 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 6d 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
Research
Goal: a thorough, cited answer to a specific question — pulled from across the whole project memory, not one file or one area. Where explore maps an area's structure, research answers a question by combining code, history, decisions, and discussion.
- Frame the question — break it into the sub-questions you must answer. State them, so the synthesis can be checked against them at the end.
- The code —
search "<sub-question>"for the relevant files, thenread_relevant "<behavior>"for the actual functions/sections with line ranges. Use theextensions/dirs/excludeDirsfilters to scope.search_symbols <name>for named things you already know. - How it connects — when the question is about relationships:
project_map(focus: <file>),depends_on/dependents <file>,impact <symbol>(transitive callers),trace from=<a> to=<b>(how one reaches another). - History & why —
search_commits "<topic>"for why and when it changed;file_history <file>for how a file evolved. - Decisions & discussion —
search_checkpoints "<topic>"for recorded decisions and direction changes;search_conversation "<topic>"for the back-and-forth and alternatives considered. - Caveats —
get_annotations(search across notes) for known bugs, constraints, and fragile spots that qualify the answer. - Verify — before asserting any claim, reopen the cited source and confirm it. Don't synthesize from snippets alone.
Finish: answer each sub-question in plain language with a file:line, commit, or checkpoint citation; separate what the source proves from what is inferred; list what stayed unresolved instead of guessing.
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.
- 6d ago First seen · 19 lines · 88 tokens per session scan A 804bfcf3673b
research is a skill published in the GitHub repository TheWinci/mimirs (29 stars, last pushed 21d ago), licensed Apache-2.0. It adds 88 tokens to every session and 491 once invoked, about $0.0004 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
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
azure-event-grid-webhooks
Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection…
baselinker-webhooks
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: orderid, state), there is NO signature…
clio-webhooks
Receive and verify Clio (Clio Manage) webhooks. Use when setting up Clio webhook handlers, debugging X-Hook-Signature verification, completing the X-Hook-Secret handshake, or handling legal practice events like matter.created, contact.updated, activity.created, or bill events.
favro-webhooks
Receive and verify Favro webhooks. Use when setting up Favro webhook handlers, debugging X-Favro-Webhook signature verification, accepting the setup ping, or handling card events (card.created, card.committed, card.moved, card.updated, card.deleted) and comment events (comment.created, comment.updated…