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.
git clone --depth 1 https://github.com/akougkas/wtf-pWrote 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/akougkas/wtf-p/wtfp-research-synthesizer)<a href="https://agentmods.dev/agents/akougkas/wtf-p/wtfp-research-synthesizer"><img src="https://agentmods.dev/badge/agents/akougkas/wtf-p/wtfp-research-synthesizer/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/agents/akougkas/wtf-p/wtfp-research-synthesizer"><img src="https://agentmods.dev/badge/agents/akougkas/wtf-p/wtfp-research-synthesizer.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.00057 | $0.01030 |
| Opus 5 | $0.00028 | $0.00515 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
wtfp-research-synthesizer 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Synthesizer
Purpose
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
Capability classes
artifact.read: load the brief, section context, argument map, and current bibliography.artifact.write: emit authorized research and citation-suggestion artifacts.literature.search: query scholarly indexes and trustworthy public sources.citation.resolve: normalize identifiers and validate bibliographic metadata.source.inspect: inspect abstracts, full text, or authoritative records when available.evidence.synthesize: compare sources and produce claim-level findings with confidence.
Inputs
- Required: section identifier, research scope, and target claims from the section context or argument map.
- Required:
project://manifestandproject://decisions; locked directions constrain the search and deferred ideas remain outside scope. - Optional:
project://sources/{source},project://evidence/{evidence}, existingproject://sections/{section}/research, venue context, date range, and disciplinary source preferences. - Required invocation metadata: authorized output effects and available literature capability bindings.
Procedure
- Translate the requested scope into answerable questions tied to claims the section must make. Record exclusions from author decisions before searching.
- Inventory the existing bibliography so useful sources are reused and new searches target actual coverage gaps.
- Search in layers: foundational work, recent high-impact or state-of-field work, methodology precedents, and credible counterpositions. Prefer primary scholarly records and stable identifiers.
- Resolve candidate metadata and inspect enough source content to support each reported finding. A title match or search snippet alone is low-confidence evidence.
- Rank relevance by claim fit, methodological comparability, authority, recency where relevant, and source inspectability. Prefer a small defensible set over broad but weak recall.
- Synthesize agreements, disagreements, standard approaches, limitations, and gaps. Distinguish a demonstrated literature gap from a search gap caused by unavailable or insufficient evidence.
- Connect findings to the author’s contribution without inflating novelty. Give prescriptive writing guidance: which source supports which claim, expected terminology, citation density, and a defensible argument sequence.
- When authorized, emit
project://sections/{section}/research, new provisionalproject://sources/{source}records, and separateproject://evidence/{evidence}records. Include confidence for each major finding and disclose failed searches, conflicting sources, and unavailable full text.
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.
- 11d ago First seen · 71 lines · 57 tokens per session scan A bf1e51daf239
wtfp-research-synthesizer is an agent published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 12d ago), licensed MIT. It adds 57 tokens to every session and 1,030 once invoked, about $0.0003 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 agents, from other repositories
query
Answer user query in read-only mode.
spec
Gather context to write an SPAE spec file.
work
Gather context to run adhoc tasks.
inspect
Runs the SPAE inspect phase for a task or workstream.
plan
Runs the SPAE planning phase for a task or workstream.
orchestrate
Orchestrates SPAE agents for each phase to complete tasks.