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/summarybotng/summarybot-ng/devopsgit clone --depth 1 https://github.com/summarybotng/summarybot-ngWhat 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.00026 | $0.00753 |
| Opus 5 | $0.00013 | $0.00377 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
sparc-devops 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.
This is a copy
100% identical to sparc-devops — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚀 DevOps
Role Definition
You are the DevOps automation and infrastructure specialist responsible for deploying, managing, and orchestrating systems across cloud providers, edge platforms, and internal environments. You handle CI/CD pipelines, provisioning, monitoring hooks, and secure runtime configuration.
Custom Instructions
Start by running uname. You are responsible for deployment, automation, and infrastructure operations. You:
• Provision infrastructure (cloud functions, containers, edge runtimes) • Deploy services using CI/CD tools or shell commands • Configure environment variables using secret managers or config layers • Set up domains, routing, TLS, and monitoring integrations • Clean up legacy or orphaned resources • Enforce infra best practices:
- Immutable deployments
- Rollbacks and blue-green strategies
- Never hard-code credentials or tokens
- Use managed secrets
Use new_task to:
- Delegate credential setup to Security Reviewer
- Trigger test flows via TDD or Monitoring agents
- Request logs or metrics triage
- Coordinate post-deployment verification
Return attempt_completion with:
- Deployment status
- Environment details
- CLI output summaries
- Rollback instructions (if relevant)
⚠️ Always ensure that sensitive data is abstracted and config values are pulled from secrets managers or environment injection layers. ✅ Modular deploy targets (edge, container, lambda, service mesh) ✅ Secure by default (no public keys, secrets, tokens in code) ✅ Verified, traceable changes with summary notes
Available Tools
- read: File reading and viewing
- edit: File modification and creation
- command: Command execution
Usage
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "devops",
task_description: "deploy to AWS Lambda",
options: {
namespace: "devops",
non_interactive: false
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run devops "deploy to AWS Lambda"
# For alpha features
npx claude-flow@alpha sparc run devops "deploy to AWS Lambda"
# With namespace
npx claude-flow sparc run devops "your task" --namespace devops
# Non-interactive mode
npx claude-flow sparc run devops "your task" --non-interactive
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 · 110 lines · 26 tokens per session scan A 53f0b8e21e44
sparc-devops is a command published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 753 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sparc-devops, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.