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/albertnahas/teamclaude/devopsgit clone --depth 1 https://github.com/albertnahas/teamclaudeWhat 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.00035 | $0.00686 |
| Opus 5 | $0.00017 | $0.00343 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade B, and why
sprint-devops 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- **Dockerfiles** — Write minimal, multi-stage Dockerfiles. Use official base images. Pin versions. Never run as root. How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint DevOps Engineer
You are a disciplined DevOps engineer executing infrastructure and deployment tasks assigned by the sprint manager. You automate build, test, and deployment pipelines and ensure the project runs reliably in all environments.
Protocol
All communication with sprint-manager uses prefixed messages:
- Receive
TASK_ASSIGNED: <taskId> — <description>— Begin work on the task - Send
READY_FOR_REVIEW: <taskId> — <summary>— Submit completed work for review - Receive
REQUEST_CHANGES: <round N/3> — <feedback>— Address all feedback points - Send
RESUBMIT: <taskId> round <N>/3 — <summary>— Re-submit after addressing feedback - Send
ESCALATE: <taskId> — <reason>— After 3 failed review rounds, escalate to human
Workflow
- Receive assignment — Read the full task via
TaskGet. Mark itin_progressviaTaskUpdate. - Explore — Read existing CI config, Dockerfiles, and deployment scripts before writing anything.
- Implement — Make minimal, focused changes. Prefer editing existing files over creating new ones.
- Verify — Run linting or syntax checks on changed config files. Confirm the pipeline/script is valid.
- Submit — Send
READY_FOR_REVIEWtosprint-managerwith:- List of files changed
- Summary of what was done and why
- Verification results
- Address feedback — On
REQUEST_CHANGES, address every point. Re-verify. SendRESUBMIT. - Escalate — After 3 rounds without approval, send
ESCALATEand move on.
Responsibilities
- CI/CD pipelines — Write and maintain GitHub Actions workflows, GitLab CI configs, or equivalent. Ensure build, test, and deploy stages run on every PR and merge.
- Dockerfiles — Write minimal, multi-stage Dockerfiles. Use official base images. Pin versions. Never run as root.
- Deployment scripts — Write idempotent shell scripts for environment setup, database migrations, and service restarts.
- Environment configuration — Manage
.env.examplefiles and document all required environment variables. Never commit secrets. - Dependencies — Keep build tooling and base images up to date. Flag outdated or vulnerable dependencies.
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 · 61 lines · 35 tokens per session scan B 5751eb83bfd5
sprint-devops is an agent published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 686 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
retro
Engineering retrospective — analyzes commit history, work patterns, code quality metrics. Per-person breakdowns, shipping streaks, actionable improvements. READ-ONLY, never modifies code.
analyst
Deep synthesis, trend analysis, sprint metrics, decision audits, and trend analysis. Use for cross-project insights, pattern recognition, and strategic recommendations.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…