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-hypothesesgit 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-hypotheses)<a href="https://agentmods.dev/skills/forger-labs-hq/researchforge/researchforge-hypotheses"><img src="https://agentmods.dev/badge/skills/forger-labs-hq/researchforge/researchforge-hypotheses/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-hypotheses"><img src="https://agentmods.dev/badge/skills/forger-labs-hq/researchforge/researchforge-hypotheses.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.00046 | $0.00455 |
| Opus 5 | $0.00023 | $0.00228 |
| Sonnet 5 | $0.00009 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
researchforge-hypotheses 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.
What it actually says
Generate hypotheses
Same handshake as the landscape: context out, YAML in, engine validates.
1. Re-read the context
.researchforge/synthesis/context.json (regenerate with
researchforge research context --json if stale) plus the imported
landscape (researchforge status --json shows what exists).
2. Write hypotheses
Write .researchforge/synthesis/hypotheses.yaml conforming to the embedded
schema. Each hypothesis needs:
- a falsifiable
claimandrationale; supporting_paper_ids/contradicting_paper_idsdrawn only from stored papers (the validator rejects unknown ids);- an honest
evidence_statusandnovelty_confidence— mark speculation asspeculative; do not inflate support; limitationsthe user should know before spending compute on it;- a
proposed_experimentconcrete enough to implement later.
3. Import (engine validates)
researchforge hypotheses import .researchforge/synthesis/hypotheses.yaml --json
researchforge hypotheses list --json
On validation failure, read the --json error payload, fix exactly the
listed fields, and re-import.
Next: for explore-mode projects, researchforge report build produces the
citation-backed report. For improve-repository projects, continue with the
researchforge-baseline skill.
Rules
- The Python engine is the boundary: never work around a validation error, a protected path, or an approval gate — fix the artifact or ask the user.
- Approvals belong to the user: never pass
--yesor type a confirmation unless the user explicitly approved that step in this conversation. - Ground every summary in stored data: quote only numbers returned by
--jsonoutput or files under.researchforge/— never invent metrics.
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 · 51 lines · 46 tokens per session scan A 1f126305cc23
researchforge-hypotheses is a skill published in the GitHub repository forger-labs-hq/researchforge (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 46 tokens to every session and 455 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
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.
statistical-method-design
Design statistical methods, baselines, diagnostics, variants, and ablations that directly address a formal problem formulation.
experimental-design
Best practices for designing reproducible ML experiments. Use when planning ablations, baselines, or controlled experiments.
ads-linkedin
Audit LinkedIn Ads measurement, Insight Tag and conversions, professional audiences, lead generation, ABM, creative, bidding, budgets, pacing, automation, and policy. Use for LinkedIn Ads, Campaign Manager, Insight Tag, Lead Gen Forms, Thought Leader Ads, ABM campaigns, or B2B paid media.
ads-launch
Draft or explicitly apply a paid-ad campaign launch through Claude Ads capability-gated adapters. Use for campaign creation, launch plans, publishing ads, activating campaigns, uploading creative, or requests to push a campaign live.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.