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 Ahmad-Jaradat-Space/co-scientist-plugin --skill grounding-claimsgit clone --depth 1 https://github.com/Ahmad-Jaradat-Space/co-scientist-pluginWrote 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/ahmad-jaradat-space/co-scientist-plugin/grounding-claims)<a href="https://agentmods.dev/skills/ahmad-jaradat-space/co-scientist-plugin/grounding-claims"><img src="https://agentmods.dev/badge/skills/ahmad-jaradat-space/co-scientist-plugin/grounding-claims/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/ahmad-jaradat-space/co-scientist-plugin/grounding-claims"><img src="https://agentmods.dev/badge/skills/ahmad-jaradat-space/co-scientist-plugin/grounding-claims.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.00088 | $0.01078 |
| Opus 5 | $0.00044 | $0.00539 |
| Sonnet 5 | $0.00018 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
grounding-claims 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grounding claims
Machine-generated hypotheses cite real-looking sources that sometimes do not say what the text claims. This skill checks that, one claim at a time. Run it before anything leaves the session: a shared write-up, a grant paragraph, a decision to run an experiment.
What gets checked
For each factual claim:
- Does the url resolve?
- Does the excerpt actually appear on that page?
- Does the source support the claim, or merely mention the topic?
- Does it support the direction of the claim? Activation is not inhibition, correlation is not causation, mouse is not human.
Check 4 catches the most errors. A source that discusses the right molecules in the wrong direction reads as support to anyone skimming.
Where the sources are
co-scientist:hypothesis_getreturns the hypothesis, its reviews, and itsartifact. The citation list with urls and excerpts is in there: atartifact.citationsfor an agent-recorded hypothesis, and underartifact.recordfor one the engine's Generation agent wrote.- Review evidence rows carry
claim,urlandexcerpt, which is exactly the triple you need. - Tool provenance from a session run records which urls an agent actually opened. A citation that appears in a hypothesis but in no tool call was not read by the agent that cited it. Treat those first.
Workflow
- [ ] 1. Extract every factual claim with its source
- [ ] 2. Fetch each source
- [ ] 3. Verdict each claim
- [ ] 4. Record the finding
- [ ] 5. Report
1. Extract
List the claims as a table before checking anything: claim, url, excerpt. Work from the list. Checking claims as you read prose means missing the ones stated without a citation at all, which are the worst kind.
Claims with no source go in the list too, marked as uncited.
2. Fetch
Fetch each url. Search the page for the excerpt. If the page is paywalled, try the abstract, the preprint, or the DOI landing page, and say which one you checked.
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 · 109 lines · 88 tokens per session scan A 4c7e3d589fd7
grounding-claims is a skill published in the GitHub repository Ahmad-Jaradat-Space/co-scientist-plugin (0 stars, last pushed 22d ago), licensed Apache-2.0. It adds 88 tokens to every session and 1,078 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
TEMPLATE
../../../agents/personas/TEMPLATE.md.
document-service
This skill should be used when the user asks to "analyze this codebase", "document this service", "generate technical docs", "I inherited this code", "help me understand this system", "create docs for this project", "what does this system look like", "onboard me to this codebase", "this codebase has no docs"…
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…
directory-management
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agentmemory/) and resolves project naming.
ov-experience-memory
Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational…
experience_loader
Load relevant OpenViking experience memories via case-linked experience candidates before solving a task.