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/binary-husky/alphaautoresearch/worker_experimentnpx skills add binary-husky/AlphaAutoResearch --skill worker_experimentgit clone --depth 1 https://github.com/binary-husky/AlphaAutoResearchWhat 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.00000 | $0.05137 |
| Opus 5 | $0.00000 | $0.02568 |
| Sonnet 5 | $0.00000 | $0.01027 |
| Haiku 4.5 | $0.00000 | $0.00514 |
Grade A, and why
worker_experiment scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
r = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Task
Before doing anything, create a log file ${exp_result_dir}/experiment_log.md, refer to the blueprint to get ${exp_result_dir}.
- Run the experiment according to the experiment blueprint.
- when execute training commandline, record your command into
${exp_result_dir}/experiment_log.md.
- when execute training commandline, record your command into
- Wait for the experiment to finish, error or time out.
- If the experiment fails, attempt to fix it and document the debugging process (
${exp_result_dir}/experiment_log.md). If it cannot be fixed, skip to step 5. - Place comprehensive experiment results in the designated location (
${exp_result_dir}/experiment_log.md). - Create a
finish.flagfile in [exp_result_dir] to mark the task as complete. - Done.
Experiment Blueprint:
Experiment blueprints are designed to execute experiments that validate hypotheses or gather necessary data. An experiment blueprint is a markdown file (blueprint.md). It contains 7 sections — you should execute the task based on this information:
- [exp_purpose] Experiment purpose (text): Briefly describe the main purpose of this experiment and the key differences from other blueprints (e.g., which hyperparameter or environment variable differs).
- [exp_codebase_dir] Main experiment code path (absolute path): The absolute path containing all code needed to run the experiment. Relatively small in size. Does not include the Python virtual environment. Remember to cd to this path before starting the experiment.
- [exp_venv_exe] Python virtual environment path (absolute path to python executable): Path to the Python executable. E.g.: /mnt/data_cpfs/agentjet/project/.venv/bin/python
- [exp_yaml_path] Experiment config file path (absolute path) (may not exist in swarm training mode): Path to the experiment configuration YAML file. This file must be located within the main experiment code path. E.g.: /mnt/data_cpfs/agentjet/project/tests/bench/benchmark_math/benchmark_math.yaml
- [exp_launch_command] Training execution command (string): E.g. python -m ajet.launcher --conf tests/bench/benchmark_math/benchmark_math.yaml --skip-check-avail-gpu --with-ray
- [exp_result_dir] Result data storage path (absolute path): Path for output data storage
- [exp_max_time] Maximum runtime is ${MaxTime}; each experiment is forcefully terminated after ${MaxTime}
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.
- 2d ago First seen · 367 lines · 0 tokens per session scan A 07976c9805c1
worker_experiment is a skill published in the GitHub repository binary-husky/AlphaAutoResearch (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,137 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…