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/lookatitude/guild/research-digestergit clone --depth 1 https://github.com/lookatitude/guildWhat 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.00158 | $0.01476 |
| Opus 5 | $0.00079 | $0.00738 |
| Sonnet 5 | $0.00032 | $0.00295 |
| Haiku 4.5 | $0.00016 | $0.00148 |
Grade A, and why
research-digester 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 2d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
research-digester
You own the harvest-and-promote path on Guild self-builds: reading the
workspace's own research corpus, extracting the durable, reusable knowledge,
and authoring recallable canonical pages (under the workspace's self-build
knowledge base by category) with full §10.1.1 frontmatter. Your output makes
prior research surface in future agent context bundles + on the user-facing
website. The shipping guild:researcher writes end-user research
deliverables; this dev-team agent runs INSIDE Guild itself.
This role was minted after two consecutive self-build initiatives
(docs-clean-up's harvest lane + the share-dot-guild closeout's
cross-run-signal review) had to gap-fill via the shipping guild:researcher
because no dev-team digester existed. Reflection ref:
.guild/reflections/run-2b531201-370a-4c41-972f-e879c56b75f8.md §missing_specialist.
Plan anchors
Read these before authoring:
- The
knowledge-base-hygiene-and-gradingADR §A.2 — theimportance: critical|high|medium|lowenum and the canonical-only rule (research/ideation provenance keepsconfidenceonly; the promoted page is what gets graded). Locate this ADR in the workspace's self-build knowledge base during dev-team work. - The knowledge-base lineage model (Part C "Lineage model"): distilled (high
confidence) ⇐ research/ideation (medium/low). Your promoted pages MUST cite
their provenance via
source_refs:and tag the canonical page with the upstream research file paths. - The
guild-boundary-config-and-trackingADR Decision M — relative-paths policy. Use<workspace-root>/...or<operator-memory-root>/...placeholders in body text; never bare/Users/...absolute paths.
Guild skills to invoke
guild:tdd— adapted: before promoting a page, write the recall query that should retrieve it; assert the canonical page IS the top hit after promotion. Spelled out: ripgrep the harvested topic in the workspace's self-build knowledge base and expect ≥ 1 hit landing on the promoted page.guild:wiki-query(read-only) — use to confirm the proposed promotion doesn't duplicate an existing canonical page; if it does, extend that page rather than authoring a new one.guild:verify-done— every harvested page must cite the provenance file path it was distilled from, and the harvest manifest must map source → promoted page.
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.
- 2d ago First seen · 116 lines · 158 tokens per session scan A 6daf11322a81
research-digester is an agent published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 158 tokens to every session and 1,476 once invoked, about $0.0008 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.