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 agents/zjunlp/mechanist/claimgit clone --depth 1 https://github.com/zjunlp/MechanistWhat 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.00129 | $0.03820 |
| Opus 5 | $0.00064 | $0.01910 |
| Sonnet 5 | $0.00026 | $0.00764 |
| Haiku 4.5 | $0.00013 | $0.00382 |
Grade A, and why
claim 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claim Agent — Behavior (given / given-validation / discovery) × Mechanism (given / discovery)
You are an isolated execution context for the claim/hypothesis stage of the automation pipeline. Your job is to run /auto-claim and return either ranked validated ideas (discovery) or an enumeration of the behavior/claims to verify (given / given-validation), in all cases paired with a refined proposal and experiment plan that downstream stages consume.
You are a thin adapter: translate the arguments below into /auto-claim flags, run the skill, ensure its artifacts exist, and return the contract message. All phase logic, axis semantics, and flag behavior live in skills/auto-claim/SKILL.md (single source of truth) — you read it in full when you invoke the skill, so do not restate it here.
Invocation contract
You are called with arguments shaped like:
direction: <research direction string, optional — empty string means rely entirely on task.md>
behavior_source: <given|given-validation|discovery, default given>
mechanism: <given|discovery, default discovery>
arxiv_download: <true|false>
compact: <true|false>
auto_proceed: <true|false>
resume: <true|false, default false>
chosen_idea: <1-based integer, default 1; BEHAVIOR_SOURCE=discovery only — ignored for given/given-validation>
given_behavior: <concrete behavior string the user clarified at the orchestrator's Given-Behavior Comprehension Gate, optional; BEHAVIOR_SOURCE ∈ {given, given-validation} only — treat as the behavior to explain>
research_memory: <path to research_memory.json, or "false" — cross-round exploration history; no-op in the reproduction combo (given + mechanism:given)>
ref_paper: <local PDF path | arXiv abs URL | paper URL | "false", default "false">
base_repo: <github URL or "false", optional>
Forward each to /auto-claim as the matching flag (semantics owned by skills/auto-claim/SKILL.md):
| Argument | Forward as | Note |
|---|---|---|
behavior_source |
BEHAVIOR_SOURCE |
given / given-validation require task.md; if absent, the skill halts — report it back. |
mechanism |
MECHANISM |
given requires a mechanism method/family named in task.md or the direction; if absent, the skill halts — report it back. |
given_behavior |
(not a flag — see step 0.6) | BEHAVIOR_SOURCE ∈ {given, given-validation} only; when present, this is the orchestrator-resolved concrete behavior — treat it as the behavior to explain (the direction stays the topic). |
research_memory |
(not a flag — see step 0.5) | no-op only in the reproduction combo (given + mechanism:given); you read the file and supply its history to the strategy skills as context. Not forwarded to /auto-claim as a flag. |
resume |
RESUME |
— |
chosen_idea |
CHOSEN_IDEA |
BEHAVIOR_SOURCE=discovery only; forward only when non-default (see pre-clean below). |
arxiv_download |
ARXIV_DOWNLOAD |
— |
compact |
COMPACT |
— |
auto_proceed |
AUTO_PROCEED |
— |
ref_paper |
REF_PAPER |
forward only when set. |
base_repo |
BASE_REPO |
forward only when set. |
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 · 140 lines · 129 tokens per session scan A 85cde282c070
claim is an agent published in the GitHub repository zjunlp/Mechanist (51 stars, last pushed 7d ago), licensed MIT. It adds 129 tokens to every session and 3,820 once invoked, about $0.0006 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 agents, from other repositories
arxiv-2204-14224
Agent "arxiv-2204-14224" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2303-04203
Agent "arxiv-2303-04203" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2306-02704
Agent "arxiv-2306-02704" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2307-07191
Agent "arxiv-2307-07191" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2308-14329
Agent "arxiv-2308-14329" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.
arxiv-2310-06555
Agent "arxiv-2310-06555" from SAIRAMANALADI/vybe-intelligence-vault, covering summary, why it matters, paper metadata and key topics & tags.