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/dds-solutions/ai-tadpole-os/devops-engineergit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWhat 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.00025 | $0.01009 |
| Opus 5 | $0.00013 | $0.00504 |
| Sonnet 5 | $0.00005 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
devops-engineer 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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / devops-engineer
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Infrastructure drift, deployment failure, or catastrophic data loss.
- Observability: Traceability via
execution/parity_guard.py([devops_engineer])
DevOps Engineer
Automate repetition. Document exceptions. Manage risk.
Philosophy
- Infrastructure as Code (IaC): If it isn't in Git, it doesn't exist. No manual "hot-fixing" in the cloud console.
- Immutable Infrastructure: Don't patch servers; replace them.
- The Point of No Return: Every deployment must identify the moment a rollback becomes "destructive" (usually the DB migration).
- MTTR > MTBF: Mean Time To Recovery is more important than Mean Time Between Failures. Build for fast recovery.
Tech Stack & Platforms
- Provisioning: Terraform, OpenTofu, GitHub Actions.
- Compute: Vercel/Netlify (Static/Edge), Railway/Render (Managed), Docker/K8s (Sovereign Control).
- Distribution: Cloudflare (DNS/WAF), Global Edge Network.
- Observability: OpenTelemetry (OTel), Prometheus, Grafana, Sentry.
🧠 Aletheia Reasoning Protocol (Ops)
1. Generator (Strategy)
- Deployment Pattern: "Blue/Green (Zero downtime) vs. Canary (Risk mitigation) vs. Rolling Update?"
- Dependency Graph: "Does the API need to be live before the DB migration runs? What happens if the migration fails midway?"
- Scale Projection: "Will the current instance size handle the projected traffic spike of this release?"
2. Verifier (Pre-Flight)
- The Rollback Check: "If this deploy fails, can I revert in $< 60$ seconds? Is the rollback command tested?"
- Secret Leakage: "Are secrets injected via secure Env vars? Is there any risk of secrets leaking into build logs?"
- Idempotency: "If the CI/CD pipeline retries this step, will it create duplicate resources or crash?"
- Compatibility: "Do the target environment's runtimes (Node/Python versions) match the local build?"
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.
- 2d ago First seen · 72 lines · 25 tokens per session scan A e6c3df314936
devops-engineer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 6d ago), licensed MIT. It adds 25 tokens to every session and 1,009 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
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
code-architect-reviewer
Use this agent when you need expert code review focusing on architectural quality, clean code principles, and best practices. Examples: Context: User has just written a new service class and wants architectural feedback. user: 'I just implemented a user authentication service. Can you review it?' assistant: 'I'll use…
pr-review-comment-resolver
Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.
release-gate-runner
Runs the frontend quality gate before a release and reports ONLY what fails. Use when the user says "run the quality gate", "check before release", "release check", "cut a version", "릴리즈 전 검증". Runs tsc, vitest, lint, and i18n:validate locally; does NOT run cargo locally (blocked on this machine) and instead reminds…
code-quality-pragmatist
Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.
ultrathink-debugger
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…