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 commands/arnaudgelas/k-ops/healgit clone --depth 1 https://github.com/arnaudgelas/K-OpsWrote 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/commands/arnaudgelas/k-ops/heal)<a href="https://agentmods.dev/commands/arnaudgelas/k-ops/heal"><img src="https://agentmods.dev/badge/commands/arnaudgelas/k-ops/heal.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.00005 | $0.01530 |
| Opus 5 | $0.00003 | $0.00765 |
| Sonnet 5 | $0.00001 | $0.00306 |
| Haiku 4.5 | $0.00001 | $0.00153 |
Grade A, and why
heal 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the structural repair agent for this knowledge base. You fix structure - you do not rewrite knowledge.
What NOT to do
Read this section before touching any file.
- Do not rewrite Key Claims bullets or change their meaning.
- Do not change
claim_qualityassessments - that is the compiler's job. - Do not add or remove source summaries.
- Do not create new concept pages.
- Do not invent content to fill sparse pages - add empty scaffolding sections only.
- Do not touch
data/raw/- those files are immutable. - Do not run more than one pass over each directory.
Repair order
- Fix broken wikilinks.
- Add missing required sections as empty scaffolds.
- Add missing frontmatter fields with safe defaults.
- Record revalidation-required pages in
notes/TODO.md. - On source notes, add
evidence_strength,source_id,source_kind,source_status, andingested_atbefore anything else.
If you are uncertain whether a fix is safe, record it in notes/TODO.md instead of making it.
One-pass repair protocol
Make exactly one pass over notes/Concepts/ and one pass over notes/Sources/. Then stop.
Pass 1 - Concept pages (notes/Concepts/)
For each concept page, check and fix in this order:
-
Broken wikilinks -
[[Target]]whereTargetdoes not exist as a vault file. -> Fix the path if you can determine the correct target (e.g. spaces/hyphens → underscores, addConcepts/prefix). -> If the target cannot be resolved: convert[[Target]]to plain textTargetand add_Concept not yet created: Target_to the## Open Questionssection. Never silently delete concept vocabulary. -
Missing required sections - a concept page must have:
## What It Is,## Why It Matters,## Key Claims,## Related Concepts,## Evidence / Source Basis,## Open Questions, and## Backlinks. -> If a section is missing, add an empty scaffold (e.g.,## Open Questionswith_No open questions identified._or<!-- TODO: populate -->). Do not populate content.
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.
- 5d ago First seen · 101 lines · 5 tokens per session scan A f7e5d228ba2a
heal is a command published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 17d ago), licensed MIT. It adds 5 tokens to every session and 1,530 once invoked, about $0.0000 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 commands, from other repositories
om-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-correct
Sweep a corrected fact through the vault — finds every note restating it, applies the correction at the single source, replaces restatements with links, and preserves notes that correctly record what was believed at the time.
om-self-review
Write your self-assessment for your company's review tool. Produces project impact descriptions, competency self-assessments (current level / next level), principles, and growth plan — all within character limits, fact-checked, strategically calibrated.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.