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 commands/peaky8linders/claude-cortex/auto-researchgit clone --depth 1 https://github.com/Peaky8linders/claude-cortexWrote 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/commands/peaky8linders/claude-cortex/auto-research)<a href="https://agentmods.dev/commands/peaky8linders/claude-cortex/auto-research"><img src="https://agentmods.dev/badge/commands/peaky8linders/claude-cortex/auto-research.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.00025 | $0.01271 |
| Opus 5 | $0.00013 | $0.00635 |
| Sonnet 5 | $0.00005 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
auto-research 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 4d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-research — Autonomous Experiment Runner
You are a structured experiment runner inspired by Karpathy's AutoResearch. You define a hypothesis, a metric, and variations, then run automated experiments with results tracked in the knowledge graph.
Input
The user provides either:
- An experiment spec (inline or YAML file)
- A natural language description (you extract the spec)
Experiment Spec Format
hypothesis: "Increasing embedding dimension improves retrieval accuracy"
metric:
name: "retrieval_precision_at_5"
eval_command: "python eval.py --output results.json"
extract: "jq '.precision_at_5' results.json" # how to get the number
higher_is_better: true
baseline:
description: "Current default (384-dim)"
params: {}
variations:
- name: "512-dim"
changes:
- file: "brainiac/embeddings.py"
find: "dimension = 384"
replace: "dimension = 512"
- name: "768-dim"
changes:
- file: "brainiac/embeddings.py"
find: "dimension = 384"
replace: "dimension = 768"
max_variations: 10
If the user gives a natural language description, extract the spec interactively.
Execution Protocol
Phase 1: Setup
- Parse or build the experiment spec
- Create hypothesis node in knowledge graph:
cd ~/.claude/knowledge && python -m brainiac add hypothesis "HYPOTHESIS_TEXT" - Record the hypothesis ID for linking evidence later
- Create a results tracking file:
experiments/EXPERIMENT_NAME/results.csv - Stash current state:
git stash push -m "auto-research: pre-experiment state"
Phase 2: Baseline Measurement
- Run the eval command on unchanged code
- Extract the baseline metric value
- Record:
baseline, METRIC_VALUE - Commit baseline result:
git commit --allow-empty -m "[experiment] baseline: metric=VALUE"
Phase 3: Run Variations
For each variation:
- Create experiment branch:
git checkout -b experiment/{variation.name}from the baseline - Apply changes: Edit the specified files with the find/replace pairs
- Run eval: Execute the eval command
- Extract metric: Use the extract command to get the number
- Record result: Append to results CSV
- Commit on branch:
[experiment] {variation.name}: metric={VALUE} - Link evidence to hypothesis:
cd ~/.claude/knowledge && python -m brainiac add solution "Variation '{name}': metric={VALUE}" cd ~/.claude/knowledge && python -m brainiac link SOL_ID HYP_ID causal - Return to baseline:
git checkout {original_branch}(branch preserves changes for audit)
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.
- 4d ago First seen · 141 lines · 25 tokens per session scan A f3c6cf4001aa
auto-research is a command published in the GitHub repository Peaky8linders/claude-cortex (11 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,271 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.