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 agents/lifecycle-innovations-limited/claude-ops/daemon-agentgit clone --depth 1 https://github.com/Lifecycle-Innovations-Limited/claude-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/agents/lifecycle-innovations-limited/claude-ops/daemon-agent)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/daemon-agent"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/daemon-agent.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.00014 | $0.00950 |
| Opus 5 | $0.00007 | $0.00475 |
| Sonnet 5 | $0.00003 | $0.00190 |
| Haiku 4.5 | $0.00001 | $0.00095 |
Grade B, and why
ops-daemon-manager scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/plugins/data/ops-ops-marketplace/daemon-health.json How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
The ops-daemon is a unified background process manager (scripts/ops-daemon.sh) that supervises
all claude-ops background services. It replaces per-service launchd agents with a single
com.claude-ops.daemon launchd unit.
Services are configured in ~/.claude/plugins/data/ops-ops-marketplace/daemon-services.json.
Health is aggregated to ~/.claude/plugins/data/ops-ops-marketplace/daemon-health.json.
Commands
Start daemon
launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.claude-ops.daemon.plist
Stop daemon
launchctl bootout gui/$(id -u)/com.claude-ops.daemon
Restart daemon
launchctl kickstart -k gui/$(id -u)/com.claude-ops.daemon
Check overall health
cat ~/.claude/plugins/data/ops-ops-marketplace/daemon-health.json
Check service statuses
cat ~/.claude/plugins/data/ops-ops-marketplace/daemon-health.json | jq '.services'
Check for pending actions (e.g. reauth needed)
cat ~/.claude/plugins/data/ops-ops-marketplace/daemon-health.json | jq '.action_needed'
Tail daemon log
tail -f ~/.claude/plugins/data/ops-ops-marketplace/logs/ops-daemon.log
Tail a specific service log
tail -f ~/.claude/plugins/data/ops-ops-marketplace/logs/<service-name>.log
Action Needed
When a service requires user intervention (e.g. whatsapp-bridge restart), action_needed is set:
{
"action_needed": { "service": "whatsapp-bridge", "action": "restart" }
}
Any ops skill that reads daemon-health.json should surface this to the user immediately.
Health Output Format
{
"timestamp": "2026-04-13T15:00:00Z",
"pid": 12345,
"uptime_seconds": 3600,
"services": {
"whatsapp-bridge": { "status": "running", "pid": 67890, "last_health": "connected", "restarts": 0 },
"memory-extractor": {
"status": "scheduled",
"next_run": "2026-04-13T15:30:00Z",
"last_run": "2026-04-13T15:00:00Z"
}
},
"action_needed": null
}
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.
- 6d ago First seen · 129 lines · 14 tokens per session scan B d3516a74ebd9
ops-daemon-manager is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (185 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 950 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
AGENTS
Every persona file MUST begin with a YAML frontmatter block.