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 LigphiDonk/Oh-my--paper --skill inno-experiment-devgit clone --depth 1 https://github.com/LigphiDonk/Oh-my--paperWrote 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/ligphidonk/oh-my--paper/inno-experiment-dev)<a href="https://agentmods.dev/skills/ligphidonk/oh-my--paper/inno-experiment-dev"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/inno-experiment-dev/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/ligphidonk/oh-my--paper/inno-experiment-dev"><img src="https://agentmods.dev/badge/skills/ligphidonk/oh-my--paper/inno-experiment-dev.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.00024 | $0.02664 |
| Opus 5 | $0.00012 | $0.01332 |
| Sonnet 5 | $0.00005 | $0.00533 |
| Haiku 4.5 | $0.00002 | $0.00266 |
Grade A, and why
inno-experiment-dev 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
inno-experiment-dev
Canonical Summary
Creates implementation plan, writes project code with judge feedback loop, and submits final experiment run. Use after code-survey in both Idea and Plan branches.
Trigger Rules
Use this skill when the user request matches its research workflow scope. Prefer the bundled resources instead of recreating templates or reference material. Keep outputs traceable to project files, citations, scripts, or upstream evidence.
Resource Use Rules
- Read from
references/only when the current task needs the extra detail.
Execution Contract
- Resolve every relative path from this skill directory first.
- Prefer inspection before mutation when invoking bundled scripts.
- If a required runtime, CLI, credential, or API is unavailable, explain the blocker and continue with the best manual fallback instead of silently skipping the step.
- Do not write generated artifacts back into the skill directory; save them inside the active project workspace.
Upstream Instructions
Inno Experiment Dev (Planning, Implementation, and Submission)
Merges the former inno-implementation-plan, inno-ml-dev-iteration, and the submit step of inno-experiment-submit-refine. Mirrors _create_implementation_plan (830-858), _implement_and_iterate (861-920), and the submit portion of _submit_and_refine_experiments (922-945) in run_infer_idea_ours.py.
Inputs
| Variable | Source | Description |
|---|---|---|
survey_res |
inno-idea-generation or user | The finalized selected idea (or refined_for_downstream) |
references |
pipeline config | Pre-formatted string of source papers |
updated_prepare_res |
inno-prepare-resources | JSON with reference_codebases and reference_paths |
code_survey_res |
inno-code-survey | Comprehensive implementation report / model survey notes |
dataset_description |
from prepare step / context | Description of available datasets (not in instance.json) |
core_code |
instance.json Experiment.core_code |
Absolute path when created by Dr. Claw (e.g. <project_path>/Experiment/core_code); use as-is or resolve with path.join(project_path, value) if relative |
code_references |
instance.json Experiment.code_references |
Absolute path when created by Dr. Claw (e.g. <project_path>/Experiment/code_references); use as-is or resolve if relative |
max_iter_times |
pipeline config | Max judge-iteration rounds (default 2) |
context_variables |
shared state | Mutable dict carrying state across agents |
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.
- prompts/build_iteration_query.md 2.6 KB
- prompts/build_judge_query.md 2.2 KB
- prompts/build_judge_simple_query.md 1.1 KB
- prompts/build_ml_dev_query.md 3.1 KB
- prompts/build_plan_query.md 2.1 KB
- prompts/build_submit_query.md 2.6 KB
- references/coding_plan_agent.md 2.4 KB
- references/judge_agent_instructions.md 2.2 KB
- references/ml_agent_instructions.md 3.4 KB
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 · 185 lines · 24 tokens per session scan A b4f61936470c
inno-experiment-dev is a skill published in the GitHub repository LigphiDonk/Oh-my--paper (721 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 2,664 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
template-code-project
Code-centric optimization research exemplar — gradient descent, convergence analysis, automated figures, dashboard, and publication-quality PDF.
code-review
Reviews code changes using CodeRabbit AI. Use when user asks for code review, PR feedback, code quality checks, security issues, or wants autonomous fix-review cycles.
Scientific Research
Scientific Research delivers source-aware research synthesis with evidence grading, uncertainty tracking, and clear conclusions.
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.