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/timurgaleev/memex/academic-verifynpx skills add timurgaleev/memex --skill academic-verifygit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/academic-verify)<a href="https://agentmods.dev/skills/timurgaleev/memex/academic-verify"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/academic-verify.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.00075 | $0.02132 |
| Opus 5 | $0.00037 | $0.01066 |
| Sonnet 5 | $0.00015 | $0.00426 |
| Haiku 4.5 | $0.00007 | $0.00213 |
Grade A, and why
academic-verify 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.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
academic-verify — Trace Claims to Source Data
Convention: see conventions/quality.md (via
get_skill conventions/quality) for citation rules; every verdict cites the source data, not just the author's claim about the source data.Convention: see conventions/brain-first.md (via
get_skill conventions/brain-first) for the lookup chain. This skill enforces brain-first by checking existing brain pages before issuing a fresh web search.
What this is
A claim-verification flow for academic / research statements. When a book, article, or speaker cites a study or quotes a number, this skill traces the claim through:
claim → publication → methodology section → raw data source → independent verification
At each step, it answers:
- Where does this number come from? (Self-generated? Survey? Government data?)
- What's the baseline? (Reduction from what? Over what time period?)
- Is the raw data available? (Public? Proprietary? "Available on request"?)
- Has anyone independently verified it? (Replication study? Government audit?)
- Are there confounding factors? (Other interventions, policy changes, COVID, sampling bias?)
- Is the comparison fair? (Cherry-picked comparison group? Survivorship bias?)
The output is a brain page at concepts/<claim-slug> (written via
page_put) that records the claim, the trace, and the verdict — so
future references to the same claim can re-use the verified analysis.
When to use this
- A book quotes a study and you want to confirm it's real and not miscited
- An article makes a quantified claim ("X reduced Y by 40%") that you want traced to the source data
- You're writing something that depends on a piece of research and you want to verify the underlying paper holds up
- You're updating a brain page that cites a research claim and you want to record the verification status alongside
What this skill is NOT
- Not adversarial / oppo work. The point is rigor, not takedown.
- Not generic web research — use the agent's web search tooling directly for open-ended topic exploration.
- Not a brain-only lookup — that's the
querytool.
What ships with it
1 file 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.
- 6d ago First seen · 231 lines · 75 tokens per session scan A db73de0b3ba1
academic-verify is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 2,132 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-31.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…