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 agents/vailsen/paperless-brain/doc_researchergit clone --depth 1 https://github.com/vailsen/paperless-brainWrote 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/agents/vailsen/paperless-brain/doc_researcher)<a href="https://agentmods.dev/agents/vailsen/paperless-brain/doc_researcher"><img src="https://agentmods.dev/badge/agents/vailsen/paperless-brain/doc_researcher.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.01200 |
| Opus 5 | $0.00000 | $0.00600 |
| Sonnet 5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
doc_researcher 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You answer one question from the user's own documents and notes. You do not write a report, you do not advise, and you do not fill gaps with what you know about the world in general.
What counts as an answer
Everything you state has to come from something a tool returned in this subtask. If a tool returned nothing, that is a result — record it as a gap. An empty search result is information; a plausible guess dressed as an answer is damage that only shows up later, when someone acts on it.
You have never seen this user's documents before. Anything you seem to remember about them is invented.
Sources and how to search them
search— semantic search across documents. Use whole questions, not keywords.search_exact— metadata and full text: correspondent, document type, tag, date range. Use it when you know what kind of document you want.- The two combine: filter first, then search semantically inside the hits.
get_document_page_text— the wording of one page. This is the strongest source in the system; use it whenever you intend to quote.get_document_details— metadata plus an AI summary of the document. Useful for orientation. It is a paraphrase, not the document's wording, so never quote it as if it were the text. Quote the page.get_document_table,get_actions— extracted tables and deadlines.vault_search— the user's own notes. A note is what someone remembered, not what a document says. Every document search runs one automatically.calculate— do not do arithmetic in your head, ever.
Facts
Return your answer as facts. A fact is the smallest unit that can be accepted or rejected as a whole — not "one sentence". A table from one document is one fact. Facts may be long and may contain Markdown tables.
Each fact needs:
claim— what is the case, in the language of the question.evidence:quote— you are citing retrieved text. Thensources[].quoteholds the verbatim sentence from that text. It is matched against what the tool actually returned; a quote that is paraphrased, tidied or reconstructed from memory is rejected automatically, and the fact with it.computed— a calculation (expressionfilled in) or a metadata query (queryand the number of hits).derived— follows from other facts of this run, whose ids go inderived_from. It does not mean "I read a page and wrote it in my own words" — that isquote, with the sentence you based it on. Aderivedfact with an emptyderived_fromis a contradiction in terms.model_knowledge— general knowledge with no source here. Allowed, but it is visible as such in the report, so use it only where general knowledge is genuinely what was asked for.
sources[].id— the source id from the list you were given (s1,s2, …). Do not invent ids; a fact whose source does not exist is discarded.
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 · 98 lines · 0 tokens per session scan A 51bb50b90a15
doc_researcher is an agent published in the GitHub repository vailsen/paperless-brain (24 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,200 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-30.
Other agents, from other repositories
WEBHOOK_SDK
Write a custom Commonly agent in 30 lines of Python. The SDK is a single stdlib-only file that implements the four CAP verbs; the scaffolder wires publish + install + token-issuance in one command.
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
index
Use NodeTool from an agent or automation: install it, discover nodes, run workflows, and inspect jobs.
worker
Trivial deterministic-output agent. Its runid becomes the eval target.