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 skills add forger-labs-hq/researchforge --skill researchforge-plangit clone --depth 1 https://github.com/forger-labs-hq/researchforgeWrote 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/forger-labs-hq/researchforge/researchforge-plan)<a href="https://agentmods.dev/skills/forger-labs-hq/researchforge/researchforge-plan"><img src="https://agentmods.dev/badge/skills/forger-labs-hq/researchforge/researchforge-plan/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.
<a href="https://agentmods.dev/skills/forger-labs-hq/researchforge/researchforge-plan"><img src="https://agentmods.dev/badge/skills/forger-labs-hq/researchforge/researchforge-plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00041 | $0.00698 |
| Opus 5 | $0.00020 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
researchforge-plan 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan experiments
You author the plan and patches; the engine validates every layer before anything can run. One plan targets one hypothesis.
1. Export planning context
researchforge experiment plan <hypothesis-id> --json
This writes .researchforge/experiments/context.json: the hypothesis, the
approved contract (metric, constraints, editable and protected paths,
limits), baseline metrics, repository scan, and the embedded schema for the
plan file. Read it fully before writing anything.
2. Write the plan and patches
.researchforge/experiments/plan.yamlconforming to the embedded schema:hypothesis_id,approach_summary, and one entry per experiment (key,title,change_summary,patch_file).- One unified diff per variant under
.researchforge/experiments/patches/, applying cleanly to the frozen baseline commit.
Hard constraints the engine enforces (do not fight them):
- patches may only touch
permissions.editable_paths; a patch touching a protected path is recorded as rejected at import and will never run — never edit benchmarks, evaluation code, or.researchforge/to make a metric look better; - changed files are extracted by git from the patch itself, never from your description;
- keep variants small and single-idea: the funnel measures one change at a time;
- to BUILD ON a prior result, set
parent:on an entry (another key in this plan or anexp-NNNfrom the context'sprior_experiments) — the parent's patch chain is applied first and your diff must be written against that combined state. A branched child's improvement is still measured against the baseline; report its increment over the parent separately and honestly.
3. Import (engine validates, six layers)
researchforge experiment import .researchforge/experiments/plan.yaml --json
On failure, the --json payload lists exactly what to fix (schema fields,
unknown hypothesis, patch that does not apply, protected-path violations).
Fix the plan or patch files and re-import.
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.
- 9d ago First seen · 77 lines · 41 tokens per session scan A 5cf1c87af2e2
researchforge-plan is a skill published in the GitHub repository forger-labs-hq/researchforge (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 41 tokens to every session and 698 once invoked, about $0.0002 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-31.
Other skills, from other repositories
fba-simulator
Run Flux Balance Analysis (FBA) and related constraint-based simulations using COBRApy. Covers standard FBA, parsimonious FBA (pFBA), Flux Variability Analysis (FVA), loopless FBA, gene/reaction knockouts, and carbon source swapping. Outputs flux distributions and CSV files.
flux-analyzer
Analyse FBA flux distributions to extract biological insights. Covers gene essentiality, phenotypic phase planes, flux sampling, pathway-level aggregation, secretion product prediction, and production of publication- quality figures.
gsmm-validator
Validate a COBRApy genome-scale metabolic model for mass/charge balance, stoichiometric consistency, biomass producibility, dead-end metabolites, thermodynamic loops, and GPR rule formatting. Outputs a structured validation report with errors and warnings.
stat-research-orchestrator
Orchestrate a statistical research pipeline centered on formal problem formulation, method proposal, theoretical analysis, experimental evaluation, comparison, and final result synthesis.
gsmm-builder
Build or load a genome-scale metabolic model (GSMM) using COBRApy. Covers loading from BIGG, constructing minimal models from scratch, setting medium constraints, and exporting validated .json model files.
mfa-pipeline-orchestrator
Orchestrate the full metabolic flux analysis pipeline from model loading to phenotype prediction and publication figures. Triggers when the user provides an organism name, BIGG model ID, or custom reaction list and wants end-to-end metabolic modelling run automatically.