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 commands/christopherlouet/claude-base/ops-serverlessgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-serverless)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-serverless"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-serverless.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 | $0.00000 | $0.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
ops-serverless 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.
What it actually says
SERVERLESS Agent
Deployment of serverless applications (AWS Lambda, Vercel, Cloudflare Workers).
Request context
$ARGUMENTS
Objective
Design and deploy a serverless architecture suited to the project, with cold start optimization and CI/CD integration.
Workflow
- Analyze the needs and choose the platform (AWS Lambda, Vercel, Cloudflare Workers)
- Structure the project (handlers, lib, types)
- Configure the framework (Serverless Framework, Vercel, Wrangler)
- Implement the handlers with error handling
- Optimize for cold starts (pooled connections, bundling, provisioned concurrency)
- Configure the deployment (local dev, staging, production)
- Estimate costs
Expected output
- Architecture serverless with platform justification
- Configuration (serverless.yml, vercel.json, wrangler.toml)
- Handlers implemented with suitable patterns
- Cost estimate monthly
Related agents
| Agent | Usage |
|---|---|
/ops:ops-ci |
Serverless CI/CD |
/ops:ops-monitoring |
Observability |
/ops:ops-cost |
Cloud cost optimization (FinOps) |
IMPORTANT: Optimize for cold starts - avoid heavy imports.
IMPORTANT: Use pooled database connections.
YOU MUST configure timeouts and memory according to the use case.
NEVER store state in memory - functions are ephemeral.
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 · 47 lines · 0 tokens per session scan A 56d108854f70
ops-serverless is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 295 tokens. 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-09-03.
Other commands, from other repositories
CONTEXT
Slash commands for SPEC-First development workflow.
00_plan
Analyze codebase and create SPEC-First execution plan through dialogue (read-only).
review
Review plans with multi-angle analysis (mandatory + extended + autonomous).
01_confirm
Extract plan from conversation, create file in draft/, auto-apply non-BLOCKING improvements, move to pending.
05_cleanup
Safe dead code cleanup - detect and remove unused imports and dead files with auto-apply for Low/Medium risk.
setup
Initial setup for claude-pilot plugin (includes AGENTTEAMS configuration).