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/jdanigo/hydraiaWrote 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/jdanigo/hydraia/devops)<a href="https://agentmods.dev/commands/jdanigo/hydraia/devops"><img src="https://agentmods.dev/badge/commands/jdanigo/hydraia/devops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jdanigo/hydraia/devops"><img src="https://agentmods.dev/badge/commands/jdanigo/hydraia/devops.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00266 |
| Opus 5.5 | $0.00010 | $0.00106 |
| Sonnet 5.5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
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 1mo 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.
What it actually says
Dispatch the devops-engineer agent. Detect the repo's existing platform (GitHub Actions/GitLab CI, Docker, Terraform/Pulumi) and author the requested config matching it — never introduce a new CI system without asking. Deploy steps, secret creation, cloud provisioning, and destructive infra are written as plan tasks FLAGGED FOR HUMAN APPROVAL; the agent never runs a deploy or mutates cloud state. Secrets are referenced by name only; third-party CI actions are pinned. Report files authored and the separated list of human-approval steps.
Request: $ARGUMENTS
When finished, record telemetry for this run: printf 'brief\n' > <base>/.run-complete (where <base> is the artifacts dir resolved at the storage gate — docs/hydraia/ by default, or the external dir if chosen). The Stop hook logs this run's real token/model/sub-agent usage to the local dashboard (delta-scoped per session, so it never double-counts). Do not hand-write the numbers.
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.
- 1mo ago First seen · 11 lines · 25 tokens per session scan A 76711763101e
devops is a command published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 25d ago), licensed MIT. It adds 25 tokens to every session and 266 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
ship-ci-review-loop
Command "ship-ci-review-loop" from composio-community/awesome-claude-plugins, covering phase 4: ci & review monitor loop - reference, this phase is mandatory, pr auto-review process, why all comments matter and the monitor loop algorithm.
audit-security
Check baseline CI security hygiene against the Starter Series bar — gitleaks, CodeQL, dep audit, license check, --ignore-scripts, Dependabot grouped, secret-scanning, claude-code-security-review, claude-security-guidance. Read-only, complementary to Anthropic's in-session security guidance plugin.
devops
DevOps and infrastructure with Masao (CI/CD, Docker, cloud).
sdlc-deploy
Phase 5 — Infrastructure & Deployment. Spawns devops-engineer and cloud-engineer to design CI/CD, containerization, and cloud infrastructure.
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...