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/openscientist-io/openscientist/result-interpretationnpx skills add openscientist-io/openscientist --skill result-interpretationgit clone --depth 1 https://github.com/openscientist-io/openscientistWrote 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/openscientist-io/openscientist/result-interpretation)<a href="https://agentmods.dev/skills/openscientist-io/openscientist/result-interpretation"><img src="https://agentmods.dev/badge/skills/openscientist-io/openscientist/result-interpretation.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 | $0.00014 | $0.01894 |
| Opus 5 | $0.00007 | $0.00947 |
| Sonnet 5 | $0.00003 | $0.00379 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
result-interpretation 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 5d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Result Interpretation
When to Use This Skill
- After running a statistical test
- When deciding if a hypothesis is supported or rejected
- When planning next steps based on results
Types of Results
1. Positive Finding (Hypothesis Supported)
Criteria:
- p-value < significance threshold (typically 0.05)
- Effect size is meaningful (not just statistically significant)
- Result makes biological sense
What to Do:
-
Calculate effect size - Don't rely on p-values alone
- Cohen's d for t-tests
- η² (eta-squared) for ANOVA
- Correlation coefficient for associations
-
Record the finding
update_knowledge_state( title="Clear, descriptive title", evidence="Statistical details: p-value, effect size, confidence interval", interpretation="Biological meaning" ) -
Search literature for validation
- Does this align with known biology?
- Are there papers supporting this mechanism?
- What enzymes/pathways are involved?
-
Generate follow-up hypotheses
- What explains this finding mechanistically?
- What are the downstream consequences?
- What conditions would reverse this effect?
Example:
Result: CDP-Choline Synthesis Index 35.4% higher in hypothermia (p=0.042, η²=0.29)
Interpretation:
- Statistically significant (p<0.05) ✓
- Large effect size (η²=0.29 is substantial) ✓
- Suggests Pcyt1 enzyme bottleneck
Action: Record finding, search "Pcyt1 regulation hypothermia"
2. Negative Finding (Hypothesis Rejected)
This is NOT a failure! Negative results are scientifically valuable.
Criteria:
- p-value > significance threshold
- OR effect size is trivial even if p<0.05
What to Do:
-
Document what was ruled out
- Update hypothesis status to "rejected"
- Note the p-value and confidence interval
- Record why this hypothesis seemed plausible
-
Extract insights from the failure
- What does this non-result tell us?
- What alternative explanations remain?
- Did we learn about the data structure?
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.
- 5d ago First seen · 250 lines · 14 tokens per session scan A 1d63edb285a4
result-interpretation is a skill published in the GitHub repository openscientist-io/openscientist (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,894 once invoked, about $0.0001 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
tao-run-deft-cr-its-mining
Run the mining-based DEFT improvement workflow for ITS Cosmos-Reason binary video questions, focused on the non-reasoning classification/evaluation path. Use when the user asks for a DEFT CR ITS mining workflow, traffic-camera Cosmos Reason improvement loop, collision-identification workflow with data mining, or…
tao-run-deft-object-detection
Run the full DEFT smart-data-augmentation loop for NVIDIA TAO Grounding DINO object detection: zero-shot baseline inference, KPI analysis, per-class gap analysis, SigLIP embedding of weak images, unique-neighbor mining against a source pool, ODVG dataset staging, and retraining — repeated for a fixed number of…
opengis-all
Use when navigating end-to-end GIS workflows — discover the full toolchain from GDAL data processing through GeoServer publishing to CesiumJS/OpenLayers visualization. One-stop index covering the complete open-source GIS data pipeline.
sciverse-paper-search
Use this skill for scientific literature search, evidence retrieval, paper metadata screening, and cited research synthesis with Sciverse. This LazyLLM-adapted version supports SciverseSearch search, metasearch, metacatalog, and getcontent only; it does not assume full Sciverse MCP resource or attachment APIs are…
star-code-reviewer
Review code quality, docstrings, and whether a plan's code matches what it promised. No argument reviews all of ${CODENAME}/; a PLANNAME (slug / prefix / filename) reviews that plan's files plus conformance (§3 tasks, §4 deliverables, §5 done-criterion); a path reviews that path; diff or a git range reviews changed…
star-expt-digest
Summarize experiment progress since last time — the periodic digest a progress report is written from, in date order. No argument resumes from the last digest; a PLANNAME covers that node's whole family — ancestors for context, descendants for evidence; d or a date covers a window; all covers everything. Collects each…