Borrowing it
Nothing to install: this file belongs to okuzpe/midas-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/okuzpe/midas-harness/main/.agents/skills/midas-explore/SKILL.mdgit clone --depth 1 https://github.com/okuzpe/midas-harnessWrote 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/okuzpe/midas-harness/midas-explore)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-explore"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-explore.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.1 | $0.00048 | $0.01129 |
| Opus 5 | $0.00024 | $0.00564 |
| Sonnet 5 | $0.00010 | $0.00226 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
midas-explore 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 7d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-explore — investigation outside the pipeline
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). Readpaths.statefirst when checking sprint conflicts.
Paths:
{runs}/→paths.runs. Sessions live at{runs}/explore/<slug>/(optional dir, like{runs}/qa/— not inRUNS_SUBDIRS). Active pointer:{runs}/explore/.active(slug text). Git-visible only (ADR-003). Never advancesstageor sprint gates.
Does / Does not
| Does | Does not |
|---|---|
| Append notes across turns | Replace /start-sprint or phase skills |
| Fetch/read sources the user names | Write product rules silently |
Propose /midas-capture on --end |
Touch paths.state phase fields |
Activation
At turn start, if {runs}/explore/.active exists and the user did not invoke /midas-explore
or --end, run Carryover only (below). Otherwise load this full skill on explicit invoke.
Carryover (active session, normal user message)
- Read
{runs}/explore/<slug>/meta.yaml+notes.md(slug from.active). - Append under
## Notes (chronological):- [HH:MM] **User**: <summary>/- [HH:MM] **Agent**: <understanding + plan> - Route into Open questions / Hypotheses / Actionable items / Sources as needed.
- Bump
turn_countandlast_activityinmeta.yaml. - Reply to the user's question — do not re-dump the whole skill.
Start — /midas-explore [topic]
- Conflict: if
paths.statehas a sprintstatus: active, AskQuestion once:- "Keep sprint; cancel explore" (default)
- "Start explore anyway (sprint stays active; do not implement sprint tasks here)"
- If
.activealready set → AskQuestion: close existing (--end --no-capture) and start new, or cancel. - Slug: kebab-case from topic (max 5 words); on collision append
-2,-3. - Create
{runs}/explore/<slug>/from<paths.engine>/templates/explore-meta.yaml+explore-notes.md. - Write slug to
{runs}/explore/.active. - Optional — lifecycle journal:
node <paths.scripts>/lifecycle-journal.mjs explore_start --detail "<slug>"(fail-open). - Confirm in ≤5 lines: slug, path, how to end (
/midas-explore --end).
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.
- 7d ago First seen · 80 lines · 48 tokens per session scan A 04c2e5625a14
midas-explore is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 48 tokens to every session and 1,129 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…