Borrowing it
Nothing to install: this file belongs to monarch-initiative/dismech. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/monarch-initiative/dismech/main/.claude/skills/donate-curation/SKILL.mdgit clone --depth 1 https://github.com/monarch-initiative/dismechWrote 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/monarch-initiative/dismech/donate-curation)<a href="https://agentmods.dev/skills/monarch-initiative/dismech/donate-curation"><img src="https://agentmods.dev/badge/skills/monarch-initiative/dismech/donate-curation/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/monarch-initiative/dismech/donate-curation"><img src="https://agentmods.dev/badge/skills/monarch-initiative/dismech/donate-curation.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.00112 | $0.05179 |
| Opus 5.5 | $0.00045 | $0.02072 |
| Sonnet 5.5 | $0.00022 | $0.01036 |
| Haiku 4.5 | $0.00011 | $0.00518 |
Grade A, and why
donate-curation 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 26d 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
donate-curation
Donate this Claude Code instance to dismech curation for a timeframe the user
chooses. The skill produces PRs and keeps them unblocked during the window;
the production pr-shepherd automation carries the long tail (review re-request,
the deterministic auto-merge sweep) after the window closes.
Active concurrency is 1 in this version. The skill works one disease at a
time and claims a new one only when no PR of the user's still needs the user's
own work. Parked PRs (awaiting review, or approved+green waiting to auto-merge)
may accumulate harmlessly; they do not block the next disease. The 8-parallel
design that /curate-next supports is a deliberate later scale-up.
The skill never merges, dismisses reviews, or self-approves. Those are the
reviewer's and the auto_merge_ready_prs.py sweep's job.
For a plain-language walkthrough aimed at a non-technical user (what to type, what happens each night, how to stop it), see
docs/schedule-donation.md. This file is the technical orchestrator spec.
This skill composes the Claude Code cloud-routine API (
RemoteTrigger) — the same mechanism as the built-inscheduleskill — but wired to the dismech curation loop specifically. It is nameddonate-curation, notschedule, on purpose: a project skill namedschedulecollides with the built-in one, and/scheduleresolves to the built-in generic routine-creator (which asks "what should the agent do?") rather than to this fixed claim→curate→PR loop. Always invoke it as/donate-curation.
Commands
/donate-curation— run once, now: reconcile against GitHub and either finish the one item that needs the user's work or (if nothing does) claim and curate one disease. No routine is registered./donate-curation <window> [<recurrence>] [for <expiry>]— register a recurring cloud routine for the window (see Schedule syntax), after a one-off proving fire./donate-curation status— show the active routine (cron / window / expiry) and the one in-flight item's state./donate-curation stop— disable the recurring routine and print the hard-delete link.
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.
- 26d ago First seen · 377 lines · 112 tokens per session scan A a3d0d1ae5e85
donate-curation is a skill published in the GitHub repository monarch-initiative/dismech (69 stars, last pushed today), licensed BSD-3-Clause. It adds 112 tokens to every session and 5,179 once invoked, about $0.0004 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-09-29.
Other skills, from other repositories
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.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.