A health-check skill for moflo, a local tool that supports agent memory and session infrastructure. It runs checks by default and can optionally apply automatic repairs.

Use it to audit moflo, inspect one component, or run supported fixes. It reports passing checks, warnings, failures, and whether repairs were applied.

Missing configuration, stopped background services, empty status displays, or inactive hooks can make the surrounding workflow appear broken. This identifies those problems and reports their status.

healer — Skill for Claude Code and Codex by eric-cielo: A health-check skill for moflo, a local tool that…

Install

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.

agentmods

npx agentmods add skills/eric-cielo/moflo/healer

Any agent

npx skills add eric-cielo/moflo --skill healer

Clone the repo

git clone --depth 1 https://github.com/eric-cielo/moflo

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eric-cielo/moflo/healer.svg)](https://agentmods.dev/skills/eric-cielo/moflo/healer)

Your own site

<a href="https://agentmods.dev/skills/eric-cielo/moflo/healer"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/healer.svg" alt="Measured on agentmods" height="20"></a>

Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 839 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00102	$0.00839
Opus 5	$0.00051	$0.00419
Sonnet 5	$0.00020	$0.00168
Haiku 4.5	$0.00010	$0.00084

Measured 5d ago against content hash 2bb165570130, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

healer 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.

.claude/skills/healer/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/healer — moflo Installation Healer

Thin wrapper around the flo healer CLI. All check + fix logic lives in the CLI; this skill just shells out, surfaces results in-thread, and gives one-line follow-up nudges.

Arguments: $ARGUMENTS

Procedure

Memory first (gate requirement):

mcp__moflo__memory_search { query: "doctor healer fix moflo.yaml gate hook wiring", namespace: "guidance" }

Run the CLI with the user's arguments passed through:
```
npx moflo healer --json $ARGUMENTS
```
- No args → audit-only.
- --fix → CLI runs auto-repairs after the audit.
- -c <component> → restricts to one check.
- Always include --json so output is machine-parseable.
Surface the JSON in-thread. Group by status:
- ✓ N passing (count only)
- ⚠ warnings — list name: message; flag with [auto-fixable] when the result has a fix field
- ✗ failures — same
- If --fix mode, read fixesApplied[] from the JSON payload and list {name, applied} per entry — applied=true → "fixed", applied=false → "needs manual action". The results[] array is post-fix state (re-evaluated), so report the final status.
- If --install was passed, surface claudeCodeInstall.installed from the payload.
- If --kill-zombies was passed, surface zombieScan.killed / zombieScan.found from the payload.
Nudge based on what changed. Only mention next steps for state that actually changed:
- Daemon restarted → Statusline should refresh within ~5s.
- moflo.yaml created → Review the new defaults at the project root before your next deep run.
- Hook wiring repaired → Restart Claude Code so the new SessionStart hook fires next launch.
- In audit-only mode with auto-fixable issues → Run /healer --fix to repair.

Rules

Don't re-document checks or fixes here. The CLI's --help and src/cli/commands/doctor-* are the source of truth.
Don't call flo doctor directly — use the healer alias for thematic consistency. They're equivalent CLI-side.
Don't swallow non-zero exit codes silently — surface them in the summary.
Note for users: Claude Code has its own built-in /doctor command that diagnoses Claude Code itself. This skill (/healer) diagnoses moflo, not Claude Code. The two are complementary, not duplicates. The healer rolls in the user-actionable parts of claude doctor (Claude Code version freshness vs npm latest) into its own Claude Code CLI check; the rest of claude doctor is a TUI on current releases and must be run interactively if you need its full report.

Read the full file on GitHub · 54 lines

Changes

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 · 54 lines · 102 tokens per session scan A 2bb165570130

Subscribe to this mod's changes

healer is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 839 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.

Debugging agent-orchestration ai-agents anthropic claude claude-code developer-tools

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

Hmbown/CodeWhale · 40 tokens

local-frontend-check

Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.

ascending-llc/jarvis-registry · 52 tokens

healer