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/proxy2021/enso/task_healthnpx skills add Proxy2021/Enso --skill task_healthgit clone --depth 1 https://github.com/Proxy2021/EnsoWhat 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.00044 | $0.00587 |
| Opus 5 | $0.00022 | $0.00293 |
| Sonnet 5 | $0.00009 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
task_health 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduled task health dashboard: monitor task statuses, failure rates, execution history, error classification, circuit breaker states, and drill into specific task run logs. The Team Leader's command center for scheduled task reliability.
Tool Reference
enso_task_health_overview (primary)
Get scheduled task health overview: total tasks, enabled/disabled counts, health score, failure summary, upcoming tasks, and circuit-broken tasks. Use when the user says: 'task health', 'scheduled task dashboard', 'task overview', 'how are tasks doing', 'task status'.
enso_task_health_task_list
List all scheduled tasks with status, schedule, failure counts, and next fire time. Sortable and filterable. Use when the user says: 'list tasks', 'show all tasks', 'scheduled tasks', 'task list', 'what tasks are running'.
Parameters:
filter(string): Filter: 'all', 'enabled', 'disabled', 'failing', 'circuit-broken' (default: 'all')
enso_task_health_task_runs
Get execution history for a specific task — run-by-run timeline with status, duration, errors, and error classification. Use when the user says: 'task history', 'task runs', 'show runs for', 'task execution log', 'drill into task'.
Parameters:
taskId(string): The task ID to get runs forcount(number): Number of runs to return (1-100, default: 20)
enso_task_health_failure_analysis
Analyze failures across all scheduled tasks: breakdown by error category, severity distribution, most-failing tasks, failure trends over time. Use when the user says: 'task failures', 'why are tasks failing', 'failure analysis', 'task error breakdown', 'failure trends'.
Parameters:
days(number): Time window in days (1-30, default: 7)
enso_task_health_timeline
Get a chronological timeline of recent task executions across all tasks — shows what ran, when, and whether it succeeded. Use when the user says: 'task timeline', 'recent executions', 'what ran today', 'execution history', 'task activity'.
Parameters:
hours(number): Time window in hours (1-168, default: 24)
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 46 lines · 44 tokens per session scan A 672e06724bd1
task_health is a skill published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 587 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
clawteam
Multi-agent swarm orchestration. USE THIS (not delegatetask) when the user says team/swarm/multi-agent/clawteam/parallel-agents/agent-team, or asks for multi-perspective analysis (stocks, research, code review, strategy). Spawns N Hermes workers in tmux windows with git worktree isolation, file-based inboxes, and a…
clawteam
Multi-agent swarm coordination via the ClawTeam CLI. Use when the user wants to create agent teams, spawn multiple agents to work in parallel, coordinate tasks with dependencies, broadcast messages between agents, monitor progress via kanban board, or launch pre-built team templates (hedge-fund, code-review…
openclaw-plugin
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace memory-core, does not claim plugins.slots.memory, and does not duplicate LycheeMem algorithms.
lycheemem
Forceful operating rules for using LycheeMem as the primary structured long-term memory path inside OpenClaw.
memory
Use LycheeMem as Claude Code's structured long-term memory for prior conversations, user preferences, project decisions, timelines, and durable facts.
tweetclaw
OpenClaw guide for Twitter search, follower exports, monitoring, media, and approved X automation through Xquik. Not affiliated with X Corp.