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 6ixGODD/mine --skill mine-plan-execgit 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-exec)<a href="https://agentmods.dev/skills/6ixgodd/mine/mine-plan-exec"><img src="https://agentmods.dev/badge/skills/6ixgodd/mine/mine-plan-exec/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/6ixgodd/mine/mine-plan-exec"><img src="https://agentmods.dev/badge/skills/6ixgodd/mine/mine-plan-exec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 168 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00072 | $0.02095 |
| Opus 5.5 | $0.00029 | $0.00838 |
| Sonnet 5.5 | $0.00014 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00210 |
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 15d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MINE Plan Execute
Implement one immutable Plan end to end in its registered linked worktree, verify, commit scoped work and hand off IMPLEMENTED for independent review. Never implement on Root/dev/stable, self-accept, merge, push or publish as part of execution.
Resolve identity and authority
Read AGENTS.md, requirements, Root .mine/config.toml/marker, the whole requested Plan, governing Design leaves, predecessor acceptance reports/commits and registered primary sources. Fetch the actual sources, not only a planner's paraphrase. Fresh governance roots are .mine/design/ and .mine/plan/; use actual configured paths.
Resolve Root from Git's first worktree inventory record. Query its graph show JSON. Match exact registered ID/path or the canonical alias forms: planNN / PNN / NN, including layered numeric segments and terminal -C01. Strip one invocation @ only. Require one distinct match, then use its exact stored ID in every command. Do not guess filenames, use substring matches, fill an omitted C ordinal or select another READY node. Legacy IDs are resolved only when actually present, never newly created.
Check installed version/help/MCP schemas first. Never bootstrap a future binary/Skill onto live older graph/layout. Complete active legacy work with its installed workflow; candidate commands belong only in isolated fixtures until actual release. Prefer available typed MCP tools; prepare, clarify, operations and verification use actual JSON CLI fallback where no corresponding MCP tool exists.
Admission and preparation
Inspect status/index/branch/inventory and classify existing edits: continue same-Plan work, preserve unrelated work, investigate ambiguous overlap. Dirty status is not permission to discard or duplicate an executor. Never stash/reset/clean/restore another owner's changes.
Require hard predecessors ACCEPTED with genuine reports/commits and this node READY or already IN_PROGRESS under the same owner/run. Read the complete graph wave/show snapshot, including held IN_PROGRESS/IMPLEMENTED owners, original/effective scope, policy/provenance, pending closures/checkpoints, lineage/worktree and mutable output/ generator resources. READY/wave selection is advisory, not a write grant. Missing required semantic policy fails closed, never downgrades or drops a held owner.
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.
- 15d ago Changed · -96 lines 2158562eb7e2
- 2mo ago Changed 0d47cd57afb5
- 2mo ago First seen · 267 lines · 72 tokens per session scan A ea7503e488ec
mine-plan-exec is a skill published in the GitHub repository 6ixGODD/mine (16 stars, last pushed 2d ago), licensed MIT. It adds 72 tokens to every session and 2,095 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
loop-it
An automated workflow that repeatedly fetches open GitHub issues, orders them by dependencies, implements them, reviews the changes, and ships them.
ship-it
A GitHub workflow for finishing an implemented issue: commit the relevant changes, push a branch, create a pull request, merge it, and close the issue. GitHub is a service for hosting code and reviewing changes, and a pull request is a proposed change for review.
package-release
Prepare, publish, repair, or verify package releases and changelogs. Always use for package/version release, publish, ship, tag, changelog, release notes, registry publication, documentation publication, or GitHub Release work. Distinguish package releases from application deployments before acting.
vibe-merge
Use when the user wants to "vibe-merge"/"vibe-marge" a PR or branch: independently reimplement good ideas, avoid blind merging/cherry-picking, preserve quality, and credit the contributor as co-author.
github-issues
Use gh CLI to view, triage, fix, link, create, or close GitHub Issues.
review-it
Code review closeout for Claude Code, Codex, OpenCode, DeepSeek TUI, and Antigravity CLI: local dirty changes, branch vs main, parallel tests.