research-execute

research-execute is a skill for Claude Code from Axect/magi-researchers. It costs 0 tokens per session (3,370 once invoked), scanned A, original, MIT.

A research-code runner that executes the commands defined in a research plan and saves the resulting files in a results folder. A research plan is a document describing how a study's code should be run.

In plain words
What is it for?
Running planned research experiments and creating their result files between coding and later testing or visualisation.
Why use it?
It avoids guessing which command or program to run and keeps execution tied to the project's written plan.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Codex.

Part of the magi-researchers plugin — 9 skills shipped together

Good fit Running planned research experiments and creating their result files between coding and later testing or visualisation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/axect/magi-researchers/research-execute
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 Axect/magi-researchers --skill research-execute
Clone the repo
git clone --depth 1 https://github.com/Axect/magi-researchers

Made for: Claude Code.

Or install magi-researchers, the plugin that ships this one along with the rest of its 9 skills.

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 research-execute

README.md
[![agentmods](https://agentmods.dev/badge/skills/axect/magi-researchers/research-execute/github.svg)](https://agentmods.dev/skills/axect/magi-researchers/research-execute)
Your own site
<a href="https://agentmods.dev/skills/axect/magi-researchers/research-execute"><img src="https://agentmods.dev/badge/skills/axect/magi-researchers/research-execute/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 research-execute

Your own site · 80×15
<a href="https://agentmods.dev/skills/axect/magi-researchers/research-execute"><img src="https://agentmods.dev/badge/skills/axect/magi-researchers/research-execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,370 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.00000 $0.03370
Opus 5 $0.00000 $0.01685
Sonnet 5 $0.00000 $0.00674
Haiku 4.5 $0.00000 $0.00337

Measured 9d ago against content hash 014dacabbdd8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

research-execute 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.

skills/research-execute/SKILL.md · 275 lines

How it starts

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

Research Execute Skill

Description

Executes the research code in src/ to generate result artifacts in results/. This is Phase 3.5 of the research pipeline, sitting between Implementation (Phase 3) and Testing & Visualization (Phase 4).

Reads execution commands deterministically from the YAML frontmatter of plan/research_plan.md — no keyword heuristics, no entry-point guessing. The full run command is defined once during planning and executed here.

Usage

/research-execute [path/to/output/dir]

Arguments

  • $ARGUMENTS — Optional path to the research output directory. If not provided, uses the most recent outputs/*/ directory.

Instructions

Claude-Only Mode

When --claude-only is active, there are no Gemini/Codex calls in this skill. All steps are performed by Claude directly.

Step 0: Locate Research Plan & Check Prerequisites

  1. Find the active research output directory (from $ARGUMENTS or most recent outputs/*/).
  2. Read plan/research_plan.md and parse the YAML frontmatter:
    ---
    languages: ["rust", "python"]
    ecosystem: ["cargo", "uv"]
    execution_cmd: "bash run_all.sh"
    dry_run_cmd: "bash run_all.sh --dry-run"
    expected_outputs:
      - "results/metrics.csv"
      - "results/checkpoint.pt"
    estimated_runtime: "~30 minutes"
    ---
    
  3. Prefer execution_manifest.json: Check if execution_manifest.json exists in the output directory root. If it does, read execution fields from this file instead of the YAML frontmatter:
    {
      "schema_version": "1.0.0",
      "languages": ["rust", "python"],
      "ecosystem": ["cargo", "uv"],
      "execution_cmd": "bash run_all.sh",
      "dry_run_cmd": "bash run_all.sh --dry-run",
      "expected_outputs": [
        {"path": "results/metrics.csv", "required": true},
        {"path": "results/checkpoint.pt", "required": false}
      ],
      "estimated_runtime": "~30 minutes"
    }
    
    If execution_manifest.json exists, it takes precedence over YAML frontmatter fields. If it does not exist, fall back to the YAML frontmatter (backward compatibility).
  4. If the frontmatter is missing or has no execution_cmd: announce the problem to the user and ask them to provide the execution command manually. Do not guess. Suggest adding the frontmatter to research_plan.md following the schema above.
  5. Verify src/ exists and contains at least one file.

Read the full file on GitHub · 275 lines

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. 9d ago First seen · 275 lines · 0 tokens per session scan A 014dacabbdd8

Subscribe to this mod's changes

research-execute is a skill published in the GitHub repository Axect/magi-researchers (13 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,370 tokens. 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

provider-integration

Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API…

hex/claude-council · 74 tokens

video-perception

Use when the user mentions a video file (.mp4, .mov, .avi, .mkv, .webm), a YouTube URL, asks to watch/analyze/review a video, or references video content in conversation.

jordanrendric/claude-video-vision · 51 tokens

antigravity

Run the Antigravity CLI (Gemini) as a collaborating AI inside Claude Code, with intelligent model routing across the software development lifecycle. Claude is the conductor/orchestrator — requirements, architecture, the hard 20%, verification, and review — and routes deterministic, high-volume work (scaffolding…

yuting0624/antigravity-for-claude-code · 199 tokens

notebook-kb

Use the notebook knowledge base (the local SQLite RAG /agy:notebook builds from a folder of documents) to do precise, grounded, cited work — total amounts by category, find every doc that mentions a person/organization, build a timeline, export a table — instead of re-reading prose and burning Claude's context.…

MarcosNahuel/antigravity-plugin-cc · 108 tokens

gemini-imagegen

Use when the user asks to generate, create, draw, edit, or restyle an image, or when a task needs image assets — logos, icons, illustrations, hero images, textures, photos, placeholder art, social/OG cards. Claude cannot produce raster images; a Gemini session via the agy (Antigravity) CLI has a generateimage tool…

Vallykrie/gemini-swarm-skill · 107 tokens

agy-prompting

Internal helper — how to tighten a user request into a sharp prompt for the Antigravity CLI (agy / Gemini 3.x with native web search and agentic tools).

MarcosNahuel/antigravity-plugin-cc · 40 tokens