Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/docxology/templatenpx agentmods add skills/docxology/template/manuscript-claim-verificationWrote 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/docxology/template/manuscript-claim-verification)<a href="https://agentmods.dev/skills/docxology/template/manuscript-claim-verification"><img src="https://agentmods.dev/badge/skills/docxology/template/manuscript-claim-verification/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/docxology/template/manuscript-claim-verification"><img src="https://agentmods.dev/badge/skills/docxology/template/manuscript-claim-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.01222 |
| Opus 5 | $0.00043 | $0.00611 |
| Sonnet 5 | $0.00017 | $0.00244 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
template-manuscript-claim-verification 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manuscript claim verification
Natural invoke
- "Triple-check every claim in my manuscript before arXiv"
- "Abstract numbers don't match optimization_results.csv"
- "Verify citations actually support what the prose says"
Inputs to confirm
- Project —
docs/_generated/active_projects.md. - Manuscript style — Pandoc-crossref vs registry tokens (see cross-ref skill).
Workflow
Build a claim inventory first (numbered, file:line, class: number, comparison, citation, cross-ref, method, figure reading).
Pass 1 — Source traceability: For each claim, locate backing artifact (generated variable, src/ + test, output/ file, bib key, cross-ref key). Tag BACKED / WEAK / UNBACKED. The canonical deterministic check for binding manuscript numbers/citations to registered evidence is infrastructure.validation.cli evidence <project> --fail-on-issues — run it as the machine gate for BACKED claims.
Pass 2 — Independent recomputation: Regenerate from clean; re-run validation CLI. Reconciliation table: stated | recomputed | tolerance | PASS/FAIL. UNREPRODUCIBLE = FAIL.
Pass 3 — Methodological adversary: Independent review axis — overstated claims, citation mismatch, figure/caption issues, abstract not earned by results. Tag OVERSTATED / UNSUPPORTED / MISLEADING.
Pass 4 — Reference existence (anti-hallucination): Resolve every cited reference against Crossref / OpenAlex / arXiv with the deterministic verification gate. Tag each ok / mismatch / fabricated / unverifiable / unchecked / anachronism. fabricated, mismatch, and anachronism are blocking. unchecked (offline + uncached) is an honest non-pass — re-run with --live to resolve, never treat it as clean. Distilled from the ARS hallucination taxonomy; runs fully offline against the SQLite cache once seeded.
Improve (not just report): Tighten claims; use generated-variable mechanism; fix citations/cross-refs; keep renderable format ([@key], @fig: OR [[…]] per project — never raw \cite{}/\ref{}). Update projects/<n>/AGENTS.md and README.md. Never hand-edit output/.
What ships with it
2 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.
- 9d ago First seen · 84 lines · 86 tokens per session scan A d857b231ed9b
template-manuscript-claim-verification is a skill published in the GitHub repository docxology/template (19 stars, last pushed today), licensed Apache-2.0. It adds 86 tokens to every session and 1,222 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-30.
Other skills, from other repositories
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
aerospace-engineering-technician
Use when a task needs the judgment of an Aerospace Engineering and Operations Technologist/Technician — verifying an installed fastener's preload against a drawing's torque callout via the T=K·D·F relationship, reducing strain-gauge data from a structural proof-load test into stress and checking it against an…
aviation-inspector
Use when a task needs the judgment of an Aviation Inspector — determining whether an air carrier's fleet is in compliance with an Airworthiness Directive across a maintenance-records sample, deciding where the FAA's compliance-and-enforcement ladder places a finding (compliance action vs. Letter of Correction vs.…
actor
Use when a task needs the judgment of a professional Actor — breaking down sides for a self-tape audition, preparing a character choice for rehearsal, deciding between two conflicting bookings, reading a contract offer for scale vs. scale-plus terms, or diagnosing why callbacks aren't converting to bookings.
advertising-promotions-manager
Use when a task needs the judgment of an Advertising and Promotions Manager — building a media plan backward from an objective and budget, briefing or evaluating creative against a brief, negotiating with agencies/media vendors, sanity-checking vendor-reported attribution, or reading a post-campaign debrief to…
agricultural-equipment-operator
Use when a task needs the judgment of an Agricultural Equipment Operator — calibrating planter seed population and singulation, diagnosing combine header or separator loss, sequencing planting or harvest across fields under a weather-constrained window, sizing machinery capacity in acres/hour against a season's…