mine-plan-exec

A controlled workflow for carrying out a MINE implementation plan in a separate Git worktree, which is an isolated copy of a repository for changes.

In plain words
What is it for?
Use it to implement an approved plan, run its checks, record the results, create commits, and update the plan's execution graph.
Why use it?
It keeps the plan as a fixed contract and checks dependencies, verification results, and plan status while the work is completed. This reduces the risk of changing the wrong branch or skipping required checks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/6ixgodd/mine/mine-plan-exec
Any agent
npx skills add 6ixGODD/mine --skill mine-plan-exec
Clone the repo
git clone --depth 1 https://github.com/6ixGODD/mine

Made for: Claude Code, Codex.

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,632 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00072 $0.03632
Opus 5 $0.00036 $0.01816
Sonnet 5 $0.00014 $0.00726
Haiku 4.5 $0.00007 $0.00363

Measured 2d ago against content hash ea7503e488ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mine-plan-exec 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.

plugins/mine/skills/mine-plan-exec/SKILL.md · 267 lines

How it starts

The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MINE Plan Execute

MINE Is Not Everyone's. Treat the supplied plan as an immutable execution contract. Implement it on the MINE-managed plan/<id>-<slug> branch, verify it, report it, and leave the current branch ready for review. Do not merely describe the work.

Integration: MCP tools and CLI fallback

mine-plan-exec queries and transitions plan state through two paths, in this order of preference:

  1. 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.
  2. JSON CLI (deterministic fallback) - when MCP is unavailable, call mine --format json commands. 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-exec may use:

  • mine_graph_status (no arguments) - read the current revision (carry data.revision as expected_revision before mutating).
  • mine_plan_show (id) - read the target node and verify it is READY or already IN_PROGRESS for this implementation.
  • mine_plan_start (id, owner?, run_id?) - transition READY -> IN_PROGRESS before any production-file edit.
  • mine_plan_mark_implemented (id, report, commits) - record the implementation report and commit evidence (IMPLEMENTED status).
  • mine_graph_validate (no arguments) - validate the graph after transitions.

Operations mine-plan-exec needs that are intentionally CLI-only (no MCP tool exposes them):

  • mine graph show --format json - obtain the complete authoritative node inventory for user-facing invocation resolution.
  • mine plan prepare --id <exact-stored-id> --format json - create or safely reuse the registered linked worktree before start.
  • mine plan release --id <id> --format json - if a predecessor was just accepted and the target node is still BLOCKED, release is the gate into READY. There is no MCP tool for release; it is a CLI fallback. (Normally mine-plan-create or mine-plan-review performs release; mine-plan-exec only does so when explicitly authorized to advance a just-unblocked node.)

Read the full file on GitHub · 267 lines

Changes

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.

  1. 2d ago First seen · 267 lines · 72 tokens per session scan A ea7503e488ec

Subscribe to this mod's changes

mine-plan-exec is a skill published in the GitHub repository 6ixGODD/mine (17 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 3,632 once invoked, about $0.0004 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.

Related

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…

smallnest/goal-workflow · 71 tokens

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, 批量实现, 循环实现…

smallnest/goal-workflow · 93 tokens

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, 生成卡片, 创建卡片…

smallnest/goal-workflow · 96 tokens

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".

smallnest/goal-workflow · 138 tokens

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.

smallnest/goal-workflow · 74 tokens

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检测".

smallnest/goal-workflow · 152 tokens