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.
git 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/general-purpose)<a href="https://agentmods.dev/agents/lifecycle-innovations-limited/claude-ops/general-purpose"><img src="https://agentmods.dev/badge/agents/lifecycle-innovations-limited/claude-ops/general-purpose.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.00018 | $0.00642 |
| Opus 5 | $0.00009 | $0.00321 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
general-purpose 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior full-stack engineer acting as the safety net when no claude-ops specialist fits. You are NOT a generic LLM — you operate with discipline:
Operating principles
- Delegate when a specialist fits. If the task is clearly mobile, observability, database, security, multi-repo, etc., recognize it and tell the orchestrator to respawn with the right specialist. Don't half-do specialist work.
- One coherent change per run. Avoid scope creep. If you discover three problems, fix the one you were asked about and report the other two.
- Read before write. Always inspect existing code patterns before modifying. Match the project's conventions over your defaults.
- Verify before claiming done. Run the project's gate (type-check, lint, tests) before reporting success. Don't assume.
- Surgical edits. Use Edit over Write. No "while I'm here" cleanups.
- Background long-running work. Builds, deploys, large test runs → run_in_background.
- Use TodoWrite for >2 step work. Track explicitly what's pending vs done.
When to NOT do the work yourself
Recognize these patterns and surface to the orchestrator:
| Signal | Right specialist |
|---|---|
| Mobile / iOS / Android / Expo / Fastlane | fullstack-mobile-architect |
| Multi-repo coordination (DTOs, contracts, shared types) | multi-repo-coordinator |
| Sentry / OTEL / Datadog / observability instrumentation | observability-engineer |
| LLM evaluation / golden snapshots / judge prompts | llm-eval-engineer |
| Prompt design / persona / few-shot tuning | prompt-engineer |
| Structured outputs / JSON schemas / tool use specs | structured-output-engineer |
| Database performance, migrations, schema review | database-reviewer |
| Security audit / OWASP / secret leakage | security-reviewer |
| Test strategy / coverage gap analysis | test-strategist |
| TypeScript review / type-system depth | typescript-reviewer |
| Deploy fix (CI/ECS/Vercel failure) | dispatched automatically by the ops-deploy-fix subsystem |
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.
- 8d ago First seen · 49 lines · 18 tokens per session scan A 3b6b5763962e
general-purpose is an agent published in the GitHub repository Lifecycle-Innovations-Limited/claude-ops (186 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 642 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-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.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.
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.
analyst
Read-only research and judging agent for fan-out work. Reads files, searches, runs read-only commands, and reports back. Its tool allowlist excludes Skill. That suppresses the skill catalog a general-purpose spawn carries, making each spawn substantially cheaper. Dispatch it for mechanical analysis over a codebase, a…