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/quantumbfs/sci-brain/autoresearchnpx skills add QuantumBFS/sci-brain --skill autoresearchgit clone --depth 1 https://github.com/QuantumBFS/sci-brainWrote 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/quantumbfs/sci-brain/autoresearch)<a href="https://agentmods.dev/skills/quantumbfs/sci-brain/autoresearch"><img src="https://agentmods.dev/badge/skills/quantumbfs/sci-brain/autoresearch.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.00171 | $0.01157 |
| Opus 5 | $0.00086 | $0.00579 |
| Sonnet 5 | $0.00034 | $0.00231 |
| Haiku 4.5 | $0.00017 | $0.00116 |
Grade A, and why
autoresearch 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autoresearch
One skill, four stages. State lives in <project>/research/STATE.md
(schema and template: references/state-schema.md). Each stage's procedure
is a file under references/stages/; this file decides which one applies
and then follows it in the same context.
| stage | what it produces | procedure |
|---|---|---|
| topics | topics.md — chosen topics, metrics, user-confirmed acceptance gate |
references/stages/topics.md |
| db | .knowledge/, research/INSIGHTS.md, research/database/, research/CATALOG.md; flips survey_gate |
references/stages/db.md |
| validator | research/validator/ (GOAL.md, validate CLI, manifest), sealed holdout; flips validator_gate |
references/stages/validator.md |
| run | .worktrees/attempt-NNN/, docs/discussion/ reflection reports |
references/stages/run.md |
Supporting references: references/insights-template.md (db),
references/validator-contract.md + references/negative-controls.md
(validator), references/attempt-protocol.md +
references/reflection-template.md + references/report-schema.md (run),
helpers/report.py (HTML cycle reports) and helpers/gen_campaign.py
(cross-cycle full-campaign overview).
Procedure
- Locate state. Read
<project>/research/STATE.md.- Missing → new project: ask the user for a recommended number of
attempts per cycle (suggest 10). Explain that this is a planning default,
not a fixed batch size: the agent may choose a smaller or larger cycle
when the evidence, candidate pool, cost, or available parallelism calls
for it, without exceeding the authorized attempt budget. Create
research/STATE.mdfromreferences/state-schema.md(stagetopics), record the answer asrecommended_cycle_size, then followreferences/stages/topics.md. - Readable legacy state with
batch_size→ preserve its value by migrating it torecommended_cycle_sizeon the next state write. Treat it as guidance, not a hard protocol rule. - Corrupt/unreadable → re-derive the stage from the artifact table below (earliest stage whose required artifacts are missing), show the user the derived state, and confirm with them before overwriting STATE.md. Never overwrite a readable STATE.md.
- Missing → new project: ask the user for a recommended number of
attempts per cycle (suggest 10). Explain that this is a planning default,
not a fixed batch size: the agent may choose a smaller or larger cycle
when the evidence, candidate pool, cost, or available parallelism calls
for it, without exceeding the authorized attempt budget. Create
- Verify, don't trust. Check the artifacts the recorded stage implies. If any are missing, drop back to the earliest stage whose artifacts are missing and tell the user what was expected and not found.
- Report and route. Summarize in a few sentences: stage, gates passed,
attempts completed, authorized attempts remaining. Then read the stage's
procedure file and follow it. When a stage advances
stage:in STATE.md, return to step 2 for the next stage unless the stage file says to stop for user review.
What ships with it
15 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.
- helpers/gen_campaign.py 9.3 KB runs code
- helpers/report.py 30 KB runs code
- helpers/test_gen_campaign.py 5.1 KB runs code
- helpers/test_report.py 15 KB runs code
- references/attempt-protocol.md 2.4 KB
- references/insights-template.md 1.5 KB
- references/negative-controls.md 1.8 KB
- references/reflection-template.md 7.8 KB
- references/report-schema.md 5.9 KB
- references/stages/db.md 2.7 KB
- references/stages/run.md 11 KB
- references/stages/topics.md 4.9 KB
- references/stages/validator.md 4.9 KB
- references/state-schema.md 2.2 KB
- references/validator-contract.md 2.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.
- 4d ago First seen · 76 lines · 171 tokens per session scan A f9c1ad94662a
autoresearch is a skill published in the GitHub repository QuantumBFS/sci-brain (81 stars, last pushed 7d ago), licensed MIT. It adds 171 tokens to every session and 1,157 once invoked, about $0.0009 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
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…
nature-statistics
Audit, revise, or draft manuscript statistical reporting for Nature / high-impact journal submissions. Use when the user asks to check statistical analysis sections, p values, confidence intervals, sample size, biological versus technical replicates, randomization, blinding, multiple-comparison correction, model…
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.