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/api_monitornpx skills add Proxy2021/Enso --skill api_monitorgit 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.00024 | $0.00730 |
| Opus 5 | $0.00012 | $0.00365 |
| Sonnet 5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
api_monitor 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Api Monitor
Real-time API monitoring dashboard with endpoint health, latency tracking, alerting, incident management, and webhook integrations
Available Tools
enso_api_monitor_overview (primary)
Show the API health dashboard with system status, stat cards, active alerts, and endpoint summary. Use when the user says: 'show API dashboard', 'API status', 'system health', 'monitoring overview'.
Parameters:
timeRange(string): Time range for metrics: 1h, 24h, 7d, 30d (default: 24h)
enso_api_monitor_endpoint_detail
View detailed metrics for a specific API endpoint including latency percentiles, throughput, error breakdown, and time-series data. Use when the user says: 'show endpoint details', 'drill into /api/users', 'endpoint metrics'.
Parameters:
endpointId(string): Endpoint ID to view details fortimeRange(string): Time range: 1h, 24h, 7d, 30d (default: 24h)
enso_api_monitor_alerts
View active alerts, resolved alerts, and alert rule configurations. Use when the user says: 'show alerts', 'alert rules', 'what alerts are firing', 'alert history'.
Parameters:
tab(string): Tab to show: active, resolved, or rules (default: active)
enso_api_monitor_webhooks
View and manage webhook configurations, delivery logs, and payload examples. Use when the user says: 'show webhooks', 'webhook status', 'webhook config', 'delivery log'.
Parameters:
action(string): Action: list, create, edit, test, delete (default: list)webhookId(string): Webhook ID for edit/test/delete actions
enso_api_monitor_history
View historical charts for latency, throughput, and error rates with selectable time ranges. Use when the user says: 'show history', 'latency trends', '7-day metrics', 'historical data'.
Parameters:
timeRange(string): Time range: 1h, 6h, 24h, 7d, 30d (default: 24h)metric(string): Metric to chart: latency, errors, throughput, all (default: all)
enso_api_monitor_incidents
View incident timeline, manage incidents (acknowledge, resolve), and view postmortem details. Use when the user says: 'show incidents', 'incident log', 'active incidents', 'acknowledge incident'.
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.
- yesterday First seen · 66 lines · 24 tokens per session scan A fb3badbd83ed
api_monitor is a skill published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 730 once invoked, about $0.0001 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.