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/learningmatter-mit/atomisticskills/general-workflow-plannernpx skills add learningmatter-mit/AtomisticSkills --skill general-workflow-plannergit clone --depth 1 https://github.com/learningmatter-mit/AtomisticSkillsWhat 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.00039 | $0.00674 |
| Opus 5 | $0.00019 | $0.00337 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
general-workflow-planner 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Workflow Planner
Goal
To decompose high-level scientific workflows (either sourced from literature or proposed directly by the user) into a concrete, executable sequence. This skill parses the objective and outputs a chronological "Detailed Action Plan" that feeds directly into the research_plan.md artifact, in accordance with .agents/rules/research-standards.md. Do not overcomplicate the output; it should be a straightforward list of steps.
Prerequisites
- A high-level scientific workflow proposed by the user or derived from literature review.
- Access to the
.agents/skills/registry and available MCP tools.
Instructions
-
Objective Parsing Analyze the high-level workflow to determine the key scientific steps (e.g., Structure Generation $\rightarrow$ Relaxation $\rightarrow$ Stability $\rightarrow$ Dynamics).
-
Skill Registry Mapping Scan the repository's capabilities. Map each conceptual step to existing project tools by searching the
.agents/skills/directory and available MCP tools (e.g.,mcp_mace_run_md,mcp_matgl_relax_structure). -
Dependency Construction Map the dependencies between the identified SKILLs and MCP tools:
- Identify data dependencies: The output of Step A must act as the input for Step B (e.g., the
mat-db-mpskill outputs a.cif, which serves as the input for themcp_mace_relax_structureMCP tool). - Identify parallelization opportunities if applicable.
- Identify data dependencies: The output of Step A must act as the input for Step B (e.g., the
-
Feasibility Analysis
- Verify that there is a continuous line of data flowing from the initial state to the target objective using only existing tools.
- If missing steps exist, flag them explicitly so the user knows where custom scripting or new skills are required.
-
Detailed Action Plan Generation Output a concrete, chronological list of steps required to execute the workflow. List the proposed hyperparameters for each SKILL and MCP tool (e.g.,
temperature,steps,supercell_min_length). This list is directly inserted into theDetailed Action Plansection ofresearch_plan.md.
What ships with it
1 file 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.
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 · 52 lines · 39 tokens per session scan A 8b9b05de2343
general-workflow-planner is a skill published in the GitHub repository learningmatter-mit/AtomisticSkills (154 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 674 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-30.
Other skills, from other repositories
aios-work-dispatch
Decide when a coding agent may use aios work for independent parallel work, preview the dispatch, and require explicit approval before live model execution. TRIGGER: aios work、parallel dispatch、并发派发、independent work items、独立工作项并行、多 agent 派发、multi-agent dispatch.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.
skill-constraints
Enforce browser automation safety constraints — tool usage order, anti-detection rules, screenshot discipline, and human-in-the-loop checks. Use when setting up or verifying browser/MCP tool operations, NOT for every skill execution.