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 skills add hecatehq/hecate --skill devopsgit clone --depth 1 https://github.com/hecatehq/hecateWrote 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/skills/hecatehq/hecate/devops)<a href="https://agentmods.dev/skills/hecatehq/hecate/devops"><img src="https://agentmods.dev/badge/skills/hecatehq/hecate/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/skills/hecatehq/hecate/devops"><img src="https://agentmods.dev/badge/skills/hecatehq/hecate/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.00031 | $0.00733 |
| Opus 5.5 | $0.00012 | $0.00293 |
| Sonnet 5.5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
hecate-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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hecate devops skill
Delivery-readiness review. Surfaces risk explicitly.
When to use
Anything with a CI/CD, environment, deploy, or migration footprint:
- New env vars or changed defaults.
- Schema changes across storage tiers (memory + SQLite + Postgres).
- CI/CD workflow changes.
- New public HTTP endpoints (downstream SDKs depend on them).
- Retention worker changes (new subsystem, changed cadence, retention windows).
- OTel surface changes (new spans, new metrics, new error codes).
- Release-note drafting and tag-cutting — see
../../tasks/release.mdfor the procedure (snapshot dry-run, verification gate, footguns, recovery).
Surfaces to check
- CI/CD. Which workflow files run? Will
paths-ignoreskip this change accidentally? Does the change need a[skip ci]marker, or does it require CI to actually run? - Environment. New env vars must land in
.env.exampleAND the relevantdocs/operator/,docs/runtime/,docs/contributor/, ordocs/design/page — same change, not as a follow-up. Stale env-var docs cause more on-call pages than missing features. - Config compatibility. Does an old config still boot? If not, that's a breaking change — needs a migration note in the commit body.
- Schema migrations. Which storage tiers are affected? Memory is rebuilt on
boot (fine). SQLite and Postgres need forward-compatible migrations and
roll-forward considerations. The retention worker subsystems (
traces,usage_events,audit,provider_history,model_call_events,chat_approvals) must keep mirroring. - Deploy and release risk. Is this safe to roll out behind a flag? Does it need a flag at all? What's the blast radius if it misbehaves?
- Rollback. Can this change be reverted cleanly? If a schema change is involved, is the rollback path documented?
- Observability. New code paths get OTel spans, not just log lines. Stable error codes for new failure modes (see
internal/api/error_mapping.go). Trace IDs surfaced. - Release notes. When relevant, draft them in the commit body so they're easy to lift later.
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 · 53 lines · 31 tokens per session scan A 5eff6dfbde4e
hecate-devops is a skill published in the GitHub repository hecatehq/hecate (23 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 733 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-30.
Other skills, from other repositories
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
self-host-studio
Install and self-host deco Studio (the open-source control plane) on the user's own infrastructure. Use when the user wants to install, run, self-host, or deploy Studio locally (Docker, Rancher Desktop, kind, minikube) or on Kubernetes (managed or self-managed), or asks to "install Studio", "self-host decocms"…
flutter-app
Work on a Flutter/Dart repository (one with a pubspec.yaml) in the sandbox — resolve private pub dependencies, run analyze/test, and QA the UI on an Android emulator or by compiling to web, and screenshot it. Use whenever the repo you are working in is a Flutter app, and especially before reporting that you cannot see…
slides
Create and edit presentation decks as single self-contained HTML files with a live, editable preview and print-to-PDF export. Use when the user wants slides, a deck, or a presentation.
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
brand
Create and maintain an org's brand as a folder the whole platform reads: colors, type, voice, logo and a deck theme. Use this whenever someone asks to "set up our brand", "make a brand kit", "apply our colors/fonts", or before producing branded artifacts (decks, pages, emails). One brand = one folder; everything that…