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-recall/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-recall)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-recall"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-recall/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/okuzpe/midas-harness/midas-recall"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-recall.svg" alt="Reviewed on agentmods" width="80" 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.00083 | $0.01919 |
| Opus 5 | $0.00042 | $0.00959 |
| Sonnet 5 | $0.00017 | $0.00384 |
| Haiku 4.5 | $0.00008 | $0.00192 |
Grade A, and why
midas-recall 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 10d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-recall — Context Pack (read-only resume)
Paths / state:
<paths.engine>/templates/skill-state-ritual.md(read-only) +AGENTS.md§ Path resolution.
Cheap read-only recovery. Assembles the smallest set of on-disk artifacts an agent needs to resume
mid-phase or mid-sprint — without dumping all of {product}/ into context. Never writes and never
advances stage.
vs
/midas-status: status = program counter + single next command (~6 lines). Recall = curated path list (~15 max) + ~30-line brief. Status may suggest recall; it does not replace it.vs path-pass
midas-sweep(internal): recall reads for orientation; sweep finds dead flows and ledger drift.
Full model: <paths.engine>/research/memory-model.md.
Args
| Arg | Default | Meaning |
|---|---|---|
phase |
default when stage has no active sprint |
Pack for the current lifecycle phase |
sprint |
use when sprint_execution + active sprint |
Pack for the active sprint + STM |
task |
narrow | Pack for the next unchecked task in the active sprint |
--focus "<query>" |
optional | Scored snippets over playbooks/progress/investigate (see §2b) + grep in {product}/ + rules |
Procedure
1. Read state
Load the file at paths.state. If missing → report /midas-init. Parse layout, paths, stage, stage_status, mode,
track, entry_stage, sprints[] (find status: active), phases ledger.
Resume ladder: cite <paths.engine>/templates/session-resume-precedence.md — do not restate it.
When step 4 is fresh ({paths.cache}/metrics/current-carryover.json, ok: true, matching sprint id,
generated_at ≤ 24h), seed the pack from its files[] before stage-command-table paths (dedupe).
2. Build Context Pack (max ~15 paths, ordered)
Runtime recall paths: <paths.engine>/stage-command-table.yaml per stage (parsed by
<paths.scripts>/stage-command-table.mjs for /midas-bundle recall profile). The YAML is
generated from STAGE_ROWS in that script — do not hand-edit it in the engine repo.
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.
- 10d ago First seen · 144 lines · 83 tokens per session scan A 708d2b53e629
midas-recall is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 83 tokens to every session and 1,919 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.