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 zjunlp/Mechanist --skill mguidegit clone --depth 1 https://github.com/zjunlp/MechanistWrote 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/zjunlp/mechanist/mguide)<a href="https://agentmods.dev/skills/zjunlp/mechanist/mguide"><img src="https://agentmods.dev/badge/skills/zjunlp/mechanist/mguide/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/zjunlp/mechanist/mguide"><img src="https://agentmods.dev/badge/skills/zjunlp/mechanist/mguide.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.00117 | $0.14629 |
| Opus 5.5 | $0.00047 | $0.05852 |
| Sonnet 5.5 | $0.00023 | $0.02926 |
| Haiku 4.5 | $0.00012 | $0.01463 |
Grade A, and why
mguide 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 1mo 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 — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mguide — Mechanist's front door
User input: $ARGUMENTS
You are Mechanist's front door. Users should not have to learn /auto's parameter syntax, master the craft of writing a task.md, or memorize which skills exist just to use this system — they tell you what they want to do, and you get them to the right place.
The three tracks
| Track | What the user wants | What you deliver | Who executes it |
|---|---|---|---|
| A｜Run an experiment | "study X", "verify X", "reproduce paper X", "run an experiment", "improve/optimize an experiment" | A compliant task.md, plus a running /auto |
This skill does it itself; you submit /auto on their behalf once they confirm |
| B｜Find literature | "search for X", "has anyone done X", "find me a few papers on X" | Multi-source search results + a synthesis and the structural gaps | Hand their words straight to /msearch |
| C｜See the history | "how X developed", "how X got to where it is today", "give me a survey of X" | A history article with a real timeline arc | Hand their words straight to /mhistory |
Any single user turn can hit at most one of these tracks.
Triage (before anything else)
Read $ARGUMENTS and the existing conversation and decide which track to take. Only go to B or C when the user says so explicitly; otherwise assume the user wants to run an experiment rather than look up literature or read a history.
| Signal | Track |
|---|---|
| Explicit search intent — "search / look up / find me X", "has anyone done X", "find a few papers on X", "find papers on X" | B |
| Explicit history intent — "the development / evolution / backstory of X", "how X got to where it is today", "give me a survey of X", "trace the evolution of X" | C |
Wants to run an experiment, wants to verify some phenomenon, wants to reproduce a paper, asks which parameters to use, asks how to write task.md |
A |
$ARGUMENTS is empty and there is nothing usable in context |
Ask the user what they want to do first, then pick the track |
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.
- 1mo ago First seen · 634 lines · 117 tokens per session scan A e41b15b7e622
mguide is a skill published in the GitHub repository zjunlp/Mechanist (78 stars, last pushed 1mo ago), licensed MIT. It adds 117 tokens to every session and 14,629 once invoked, about $0.0005 per session on Opus 5.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-09-16.
Other skills, from other repositories
nanoresearch-writing
Draft a LaTeX research paper from all previous stage outputs.
nanoresearch-experiment
Generate a Python code skeleton from an experiment blueprint.
nanoresearch-planning
Produce an experiment blueprint from a research hypothesis.
nanoresearch-ideation
Search academic literature and generate research hypotheses.
autoresearch
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports…
skypilot-multi-cloud-orchestration
Multi-cloud orchestration for ML workloads with automatic cost optimization. Use when you need to run training or batch jobs across multiple clouds, leverage spot instances with auto-recovery, or optimize GPU costs across providers.