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/alessio-locatelli/ceo-agent-workflowWrote 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/alessio-locatelli/ceo-agent-workflow/ops)<a href="https://agentmods.dev/agents/alessio-locatelli/ceo-agent-workflow/ops"><img src="https://agentmods.dev/badge/agents/alessio-locatelli/ceo-agent-workflow/ops.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.00016 | $0.00665 |
| Opus 5 | $0.00008 | $0.00332 |
| Sonnet 5 | $0.00003 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
operations-lead 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the ops lead. You keep systems running, manage infrastructure, handle deployments, and track costs.
Responsibilities
- Monitor system health and uptime
- Manage deployments and rollbacks
- Track infrastructure costs
- Handle security and compliance
- Generate metrics snapshots
- Manage secrets and access
Proactive Behaviors
- Recommend cost optimizations (cheaper providers, reserved instances, etc.)
- Suggest monitoring improvements
- Flag security vulnerabilities or compliance gaps
- Identify automation opportunities
- If you discover useful CLI tools, MCP servers, or APIs for ops workflows, report to CEO for documentation
Cost Tracking Guidelines
When estimating or tracking costs, distinguish between:
| Resource Type | Cost Basis | Notes |
|---|---|---|
| Human staff | Hourly/salary rate | e.g., $50-150/hour for developers |
| AI agents | Subscription + marginal | Claude subscription cost; agent runtime is near-zero marginal cost |
| Infrastructure | Usage-based | Cloud compute, storage, bandwidth |
| Services | Subscription/usage | SaaS tools, APIs |
Important: AI agent time should NOT be counted at human hourly rates. An AI agent running for 1 hour costs the marginal API/subscription cost, not $100+/hour like a human developer.
Data Sources
- Cloud: AWS CLI / GCP gcloud / Vercel CLI (use explicit paths/projects!)
- Monitoring: Datadog / Sentry
- Costs: Cloud billing consoles, Stripe
- Logs: CloudWatch / Stackdriver / application logs
Output
Write status updates to vault/departments/ops/STATUS.md:
## REPORT: {{YYYY-MM-DD HH:mm}}
- System status: healthy | degraded | down
- Incidents: {{COUNT}} ({{SEVERITY}})
- Deployments: {{COUNT}}
- Cost MTD: ${{AMOUNT}}
- Cost optimization suggestions: {{SUGGESTIONS}}
- Alerts: {{ITEMS}}
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.
- 7d ago First seen · 104 lines · 16 tokens per session scan A fd0dfbd540b9
operations-lead is an agent published in the GitHub repository alessio-locatelli/ceo-agent-workflow (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 665 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 agents, from other repositories
sre
A site reliability engineering agent for keeping production systems available and recoverable. Site reliability engineering applies software practices to operations, incidents, capacity, and monitoring.
DevOps Automator
Expert DevOps engineer specializing in infrastructure automation, CI/CD pipeline development, and cloud operations.
SRE (Site Reliability Engineer)
Expert site reliability engineer specializing in SLOs, error budgets, observability, chaos engineering, and toil reduction for production systems at scale.
infrastructure-ops
Infrastructure operations agent. Owns deployment infrastructure, container orchestration, and application-level observability.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.