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/6ixgodd/mine/mine-plan-createnpx skills add 6ixGODD/mine --skill mine-plan-creategit clone --depth 1 https://github.com/6ixGODD/mineWrote 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/6ixgodd/mine/mine-plan-create)<a href="https://agentmods.dev/skills/6ixgodd/mine/mine-plan-create"><img src="https://agentmods.dev/badge/skills/6ixgodd/mine/mine-plan-create.svg" alt="Measured on agentmods" 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 | $0.00119 | $0.05939 |
| Opus 5 | $0.00060 | $0.02969 |
| Sonnet 5 | $0.00024 | $0.01188 |
| Haiku 4.5 | $0.00012 | $0.00594 |
Grade A, and why
mine-plan-create 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 3d 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 — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MINE Plan Create
Create an implementation-ready plan from requirements, current repository evidence, the architecture source of truth, and freshly verified external documentation.
A completed plan is an executable engineering contract, not a brainstorm, backlog, generic checklist, or restatement of the user's request. Make it precise enough that a weak implementation agent can execute it without inventing product decisions, interfaces, algorithms, file ownership, tests, or verification commands.
Integration: MCP tools and CLI fallback
mine-plan-create registers and queries plans through two paths, in this
order of preference:
- MCP tools (preferred) - when the current Agent runtime exposes the
MINE MCP server (
mine mcp serve), call the typed MCP tools. They return the same DTOs as the JSON CLI and never touch the execution-graph files. - JSON CLI (deterministic fallback) - when MCP is unavailable, call
mine --format jsoncommands. Never parse human output.
Never invent an MCP tool, CLI command, flag, JSON field, or lifecycle
transition that the current binary does not expose. Never edit
docs/plan/execution-graph.toml or docs/plan/execution-graph.md directly.
The accepted MCP tools mine-plan-create may use:
mine_graph_status(no arguments) - read the current revision, branches, and plan count (carrydata.revisionas the expected revision on writes).mine_graph_validate(no arguments) - validate the graph after registration.mine_graph_ready(no arguments) - read the ready frontier.mine_plan_show(id) - look up a plan node.mine_design_readiness(scope?) - verify that applicable planning-blocking ADRs and the detailed Design are ready for the requested scope.mine_adr_show(id) /mine_adr_list/mine_adr_validate- inspect the digest-bound ADR registry before planning.mine_plan_add(id,path,title,design_references,exclusive_write_paths?,hard_predecessors?) - register a newDRAFTplan node.mine_design_validate(no arguments) - confirm design references resolve.
What ships with it
3 files 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.
- 3d ago First seen · 482 lines · 119 tokens per session scan A 90c9783b4595
mine-plan-create is a skill published in the GitHub repository 6ixGODD/mine (17 stars, last pushed 5d ago), licensed MIT. It adds 119 tokens to every session and 5,939 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 skills, from other repositories
refactor
Expert code refactoring based on Martin Fowler's catalog — improve maintainability without changing behavior. Covers code smells, composing methods, moving features, organizing data, simplifying conditionals, method calls, and generalization. Triggers on: refactor, 重构, clean up, improve code, code smell, extract…
loop-it
Automated issue loop with checkpoint/resume: fetch open GitHub issues → dependency-aware topological sort → implement each issue end-to-end → review with /review-it → ship with /ship-it → repeat. Persists state to .loop-state.json for crash recovery. Triggers on: loop-it, loop issues, auto implement, 批量实现, 循环实现…
to-issues
Decompose a PRD and/or SPEC into implementable, vertically-sliced Issues with real blocking edges, then create them in your chosen platform (GitHub or Local). Use after /prd (and optionally /prd-to-spec) to turn requirements into agent-ready tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片…
listenhub-tts
使用 ListenHub API 将文本转换为语音（TTS）。支持三种模式：快速合成（/v1/tts）、 多角色脚本（/v1/speech）、长文本流式合成（/v1/flow-speech/episodes）。 音色未指定时自动获取音色列表供用户选择，默认使用 chat-girl-105-cn（晓曼）。 Use when user says: "tts", "text to speech", "语音合成", "文字转语音", "朗读", "生成语音", "生成音频", "转音频", "text to audio".
article-icons
Illustrate an article (Markdown, HTML, etc.) with animated-style icons from itshover.com/icons. Fetches icons as clean inline SVG and places them at section headings, key concepts, lists, and callouts. Triggers on: /article-icons, 配图, 给文章配图标, add icons to article, illustrate with icons.
humanize-it
对指定文档进行去 AI 味的改写。自动选择最合适的人性化策略（humanizer-zh / humanize-chinese / technical-writing）， 迭代改写直到效果达标或迭代 42 次为止。适用于中文文本的去 AI 化处理，包括通用文章、技术文档、学术论文等。 Use when user says: "humanize this", "去AI味", "降AIGC", "人性化改写", "改成人话", "去除AI痕迹", "humanize document", "make text human-like", "去机器味", "降低AI率", "过AIGC检测".