Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/OpenCoven/covennpx agentmods add skills/opencoven/coven/coven-cloud-maintainerWrote 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/opencoven/coven/coven-cloud-maintainer)<a href="https://agentmods.dev/skills/opencoven/coven/coven-cloud-maintainer"><img src="https://agentmods.dev/badge/skills/opencoven/coven/coven-cloud-maintainer/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/opencoven/coven/coven-cloud-maintainer"><img src="https://agentmods.dev/badge/skills/opencoven/coven/coven-cloud-maintainer.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.00065 | $0.02554 |
| Opus 5.5 | $0.00026 | $0.01022 |
| Sonnet 5.5 | $0.00013 | $0.00511 |
| Haiku 4.5 | $0.00006 | $0.00255 |
Grade A, and why
coven-cloud-maintainer 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coven cloud maintainer
A session on a Cloud VM shares nothing with a session on a laptop: not the filesystem, not the git common directory, not the claim registry, not the chat. The only state both can read is GitHub. This skill defines how to read and write that state so any later session can pick work up without hidden context.
What this skill composes
It adds one layer, coordination across environments, and defers everything else. When it seems to disagree with one of these, the other document wins.
AGENTS.md: claims, task worktrees, branch and PR workflow, local gates and the Policy guard, attribution.docs/work-tracking.md: GitHub issues are the sole work tracker. This skill adds no database, cache or lock service.skills/pr-agent: the readiness packet in the PR body. A checkpoint links the PR; it does not replace the packet.skills/coven-parallel-work: the same-machine protocol (worktree isolation, claims, hooks). In this repository the AGENTS.md worktree layout andcoven claimare its implementation.
Which signal covers what
| Signal | Visible to | Tells you |
|---|---|---|
coven claim status |
worktrees sharing this checkout's git common directory | another session in this checkout is editing |
| Issue assignee | everyone | who is accountable; every session may run as the same account, so it is not a session lock |
| Latest checkpoint comment | everyone | which session and environment worked last, its branch and full SHA, what comes next |
| Open PR for the issue | everyone | the delivery vehicle to reuse instead of opening another |
Two rules follow, and neither has exceptions:
- A local claim is never a cross-VM lock. Acquire it anyway, because other worktrees of the same checkout rely on it.
- An empty claim registry never means the issue is unowned. A checkpoint from another ENVIRONMENT posted less than two hours ago means the work may be live elsewhere: comment on the issue and coordinate before editing. After that window, resume and say so in your first checkpoint.
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 · 210 lines · 65 tokens per session scan A 16c3db98dc77
coven-cloud-maintainer is a skill published in the GitHub repository OpenCoven/coven (75 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 2,554 once invoked, about $0.0003 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-11-01.
Other skills, from other repositories
mk:ghpm
GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or…
handoff
Use when ending a session and preparing for the next session — creates checkpoint, updates next-session.md, and ensures all PRs are tracked.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.