experiment-section-auditor

experiment-section-auditor is a skill for Claude Code, Codex from yujie-jason-zhang/polish_skill. It costs 194 tokens per session (2,544 once invoked), scanned A, original, MIT.

A review guide for a research paper's experiments, including comparisons, ablation studies, and the explanation of results.

In plain words
What is it for?
Plan the smallest useful set of experiments, check whether ablations are justified, and revise results writing so it stays tied to the paper's claims.
Why use it?
It checks that each experiment supports a main claim and that the results are presented as an argument rather than as disconnected numbers. An ablation study removes or changes parts of a method to test what matters.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Plan the smallest useful set of experiments, check whether ablations are justified, and revise results writing so it stays tied to the paper's claims.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yujie-jason-zhang/polish_skill/experiment-section-auditor
Install

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.

Any agent
npx skills add yujie-jason-zhang/polish_skill --skill experiment-section-auditor
Clone the repo
git clone --depth 1 https://github.com/yujie-jason-zhang/polish_skill

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for experiment-section-auditor

README.md
[![agentmods](https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor/github.svg)](https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor)
Your own site
<a href="https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor"><img src="https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor/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.

agentmods 80×15 button for experiment-section-auditor

Your own site · 80×15
<a href="https://agentmods.dev/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor"><img src="https://agentmods.dev/badge/skills/yujie-jason-zhang/polish_skill/experiment-section-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 194 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,544 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00194 $0.02544
Opus 5.5 $0.00078 $0.01018
Sonnet 5.5 $0.00039 $0.00509
Haiku 4.5 $0.00019 $0.00254

Measured 1mo ago against content hash e7fe84cbec6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

experiment-section-auditor 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 1mo 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.

experiment-section-auditor/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Experiment Section Auditor

Scope

Use this skill when the user is designing, revising, or writing the experiment section and wants a constraint layer — not an author. It covers two things and only these two:

  • experiment and ablation design: whether the study actually argues the paper's main line, and what the minimal set is under real resource limits;
  • results narration: whether results are written as argument tied to claims rather than as a report of numbers.

Read references/experiment_section_guide.md for the claim–evidence mapping method, the minimal-set-under-constraints procedure, the ablation discipline, the report-style-versus-argument checklist with rewrite examples, and the output template. For a quick check, the rules below are enough.

Use another skill when the task is primarily:

  • how the contribution — including the one-line results summary in the abstract or introduction — is framed: use paper-argument-reconstructor (if available). Pull the paper's claims from there and audit the experiments against them. That skill owns the abstract/intro wording; this one owns the results narration inside the experiment section. They must stay consistent: the abstract's results sentence must not claim more, or under looser conditions, than the section supports;
  • whether the idea is novel or what can be claimed at all: use idea-novelty-auditor (if available). That fixes the defensible claims; this checks the experiments that support them;
  • TeX-safe or final-language polishing of the section: use paper-polisher (if available);
  • choosing a target journal: use journal-recommender (if available).

This skill does not lead the experiment design and does not write the section for the user. It audits, flags, and proposes the minimum needed to support the claims. The user drives.

Verification Mode

This skill is audit-first in both modes; what changes is how much it proposes.

  • Default (the user's own plan or draft): audit against the rules below, flag gaps and report-style narration, and propose only the minimal experiment or ablation needed to close each gap. Do not rewrite the section or design a full campaign.
  • Strict verification (an experiment plan or narration another tool or skill already produced): do not propose a competing design; check claim-coverage, feasibility assumptions, over-claims, and report-style, and report only the deviations. Fix one in place only if it breaks a non-negotiable rule (a fabricated result, an experiment assumed feasible or presented as done, an invented anomaly cause, or an unconditional over-claim).

Read the full file on GitHub · 119 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 119 lines · 194 tokens per session scan A e7fe84cbec6c

Subscribe to this mod's changes

experiment-section-auditor is a skill published in the GitHub repository yujie-jason-zhang/polish_skill (24 stars, last pushed 2mo ago), licensed MIT. It adds 194 tokens to every session and 2,544 once invoked, about $0.0008 per session on Opus 5.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.

Related

Other skills, from other repositories

academic-plotting

Generates publication-quality figures for ML papers from research context. Given a paper section or description, extracts system components and relationships to generate architecture diagrams via Gemini. Given experiment results or data, auto-selects chart type and generates data-driven figures via matplotlib/seaborn.…

Orchestra-Research/AI-Research-SKILLs · 68 tokens

systems-paper-writing

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

Orchestra-Research/AI-Research-SKILLs · 66 tokens

refactor-research-code

Clean research code for public release while preserving reported results. Uses releaseaudit.py to separate safe mechanical cleanup from ask-first behavior risks and identity leaks. Use for release-ready repos, dead experiment branches, config extraction, documented entrypoints, and double-blind code cleanup.

ShaishavMaisuria/research-paper-lifecycle-skills · 60 tokens

prepare-artifacts

Prepares a reproducibility artifact (code/data) for submission and badging. Use when a researcher says "artifact evaluation", "artifact appendix", "reproducibility", "badge", "Artifacts Available/Evaluated/Functional/Reusable", "Results Reproduced/Replicated", "ACM badging", "USENIX/OSDI/SOSP AE", "SIGMOD ARI"…

ShaishavMaisuria/research-paper-lifecycle-skills · 225 tokens

simulate-reviewers

Venue-calibrated peer-review simulation. Use when a researcher says "simulate reviewers", "mock review", "review my paper like a NeurIPS reviewer", "what would Reviewer 2 say", "red-team my paper", "find weaknesses before I submit", "peer review my paper", "strengths and weaknesses / pros and cons of my paper", "what…

ShaishavMaisuria/research-paper-lifecycle-skills · 239 tokens

verify-results

Check whether reported paper metrics are consistent with outputs from the local code artifact. Use for result reproduction checks, artifact evaluation, reproducibility checklists, code-versus-paper audits, table or claim metric comparisons, and badge-readiness review.

ShaishavMaisuria/research-paper-lifecycle-skills · 50 tokens