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-syncnpx skills add 6ixGODD/mine --skill mine-syncgit clone --depth 1 https://github.com/6ixGODD/mineWhat 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.00090 | $0.02979 |
| Opus 5 | $0.00045 | $0.01489 |
| Sonnet 5 | $0.00018 | $0.00596 |
| Haiku 4.5 | $0.00009 | $0.00298 |
Grade A, and why
mine-sync 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MINE Sync
MINE Is Not Everyone's. mine-sync is MINE's code-first, high-cost synchronization Skill that makes docs/design/ an accurate description of the repository that actually exists. It is destructive to managed design by intent and bounded by strict safety rules. It is the code-authoritative counterpart to mine-arch (which is requirement-first and may deliberately diverge from current code).
This Skill's behavior is governed by docs/design/governance/design-sync.md and ADR-0005 ("Code Is the Default Authority During mine-sync"). This document states the exact procedure; any summarized version elsewhere does not override it.
Integration: MCP tools and CLI fallback
mine-sync validates the design knowledge base 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. - JSON CLI (deterministic fallback) - when MCP is unavailable, call
mine --format jsoncommands.
Never invent an MCP tool, CLI command, flag, 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-sync may use:
mine_design_validate(no arguments) - validate the design namespace (marker, index links, anchors, size thresholds).mine_graph_validate(no arguments) - validate the execution graph when a plan workspace is active.mine_graph_status(no arguments) - read the current revision and workspace.
Operations mine-sync needs that are intentionally CLI-only (no MCP tool
exposes them, because they create local recovery state or read marker
identity outside the graph):
mine design backup --format json- create the verified local design backup before any mutation (no MCP equivalent; backups are local recovery material, never tracked or exposed over MCP).mine design status --format json- marker/identity confirmation.
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 · 247 lines · 90 tokens per session scan A 57ad3088fac2
mine-sync is a skill published in the GitHub repository 6ixGODD/mine (17 stars, last pushed 4d ago), licensed MIT. It adds 90 tokens to every session and 2,979 once invoked, about $0.0005 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
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, 批量实现, 循环实现…
skill-author
Teach an author how to integrate the CAFleet-orchestrated team pattern into a new skill they are writing. Auto-load when the author intends to create a new CAFleet-orchestrated skill, write a skill that spawns cafleet members, add a Director/Member team skill, design a multi-agent broker-coordinated skill, build a…
cafleet
Interact with the CAFleet message broker and supervise CAFleet member teams. Use when an agent needs to register as a member, send/receive messages, poll inbox, acknowledge messages, or discover other members; or when a Director is about to spawn, monitor, health-check, or recover a stalled team of CAFleet members…
session-reflect
Analyze a user's pi coding-agent session history for recurring behavior, prompting habits, workflow loops, friction, and preferences. Use when the user asks to inspect or reflect on pi sessions, common behavior patterns, agent/user interaction style, prompting habits, or personal pi workflow quality.
chat-to-skill
Convert current chat session into a reusable skill. Use when user says "/chat-to-skill", "save this as skill", "create skill from chat", "turn this into a skill", or wants to preserve learnings from the conversation as long-term memory.
skill-discovery
Find agent skills and skill repositories on GitHub.