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 cdeust/zetetic-team-subagents --skill evidence-synthesisgit clone --depth 1 https://github.com/cdeust/zetetic-team-subagentsWrote 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/cdeust/zetetic-team-subagents/evidence-synthesis)<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/evidence-synthesis"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/evidence-synthesis/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/cdeust/zetetic-team-subagents/evidence-synthesis"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/evidence-synthesis.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.00063 | $0.00945 |
| Opus 5 | $0.00032 | $0.00473 |
| Sonnet 5 | $0.00013 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
evidence-synthesis 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evidence Synthesis
Turn a corpus into a traceable conclusion. Treat a conclusion as provisional unless multiple independent primary sources support it under conditions that match the question.
The bundled references are modern, reusable reconstructions grounded in the cited works. Do not present their exact workflows as historical claims that the named figures stated verbatim.
Select the reasoning references
Read every reference needed for the source shape. Combine references when the question crosses rows.
| Reference | Use it for |
|---|---|
| Cochrane | systematic search, study appraisal, heterogeneity, publication bias |
| Toulmin | claim, evidence, warrant, qualifier and rebuttal structure |
| Feynman | rederivation, plain-language integrity checks, cargo-cult detection |
| Darwin | long-horizon accumulation, difficulty books, strongest contrary case first |
| Laplace | explicit prior-to-posterior belief updates and sensitivity analysis |
| Gadamer | interpretation, pre-understanding and charitable reading |
| Strauss | open and focused coding of qualitative material |
| Geertz | behavior in context, emic/etic separation and thick description |
Workflow
- Bind the question. State the population or context, intervention or phenomenon, comparison, outcome, time horizon and decision at stake. Mark missing elements instead of silently filling them.
- Build a source ledger. Record each primary source, its design, setting, date, measured outcome, relevant passage or equation, limitations and independence from the other sources. Trace secondary claims back to the original source before relying on them.
- Verify comparability. Check that definitions, units, baselines, populations, versions and experimental conditions match. Keep incompatible evidence in separate strata.
- Make the inference visible. For every material claim, write its evidence, warrant, backing, qualifier and strongest rebuttal. Label observations, author interpretations and your own inferences separately.
- Seek disconfirmation. Search for null results, contrary cases, adverse outcomes, missing data, publication bias, alternative interpretations and dependency between nominally separate sources.
- Synthesize at the supported strength. Report agreement and disagreement, explain heterogeneity and downgrade the conclusion when evidence is indirect, dependent, incomplete or condition-mismatched. Do not invent priors, thresholds, effect sizes or missing measurements.
- Audit the draft. Re-derive key steps, explain them in plain language, verify every citation against the source and list blind spots that remain.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 89 lines · 63 tokens per session scan A 9049201e09b7
evidence-synthesis is a skill published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 945 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-31.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…
codex-test-gen
Generate unit tests for specified functions using Codex exec.