Borrowing it
Nothing to install: this file belongs to ra3orblade/swarm. 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/ra3orblade/swarm/main/.claude/skills/chores/SKILL.mdgit clone --depth 1 https://github.com/ra3orblade/swarmWrote 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/ra3orblade/swarm/chores)<a href="https://agentmods.dev/skills/ra3orblade/swarm/chores"><img src="https://agentmods.dev/badge/skills/ra3orblade/swarm/chores/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/ra3orblade/swarm/chores"><img src="https://agentmods.dev/badge/skills/ra3orblade/swarm/chores.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.00060 | $0.00488 |
| Opus 5 | $0.00030 | $0.00244 |
| Sonnet 5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
chores 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 8d 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
Chores
Drive the wrap-up in order. Between steps, surface findings — the user redirects; don't auto-fix beyond trivial mechanical items without a go-ahead. Hard-stop on must-fix findings until acknowledged.
Preconditions
- You are in a git worktree, not the shared checkout.
git rev-parse --show-toplevelshould end in.swarm/worktrees/…(or another dedicated worktree), never/Users/.../harnesswhile another session may be live. If you're in the shared tree, stop and move the work to a worktree (git worktree add ~/.swarm/worktrees/swarm/<task> -b feat/<task> origin/main). git statusshows the changes you intend to ship.
Sequence
- Verify suite — all must pass:
Fix mechanical failures (formatting viabun run typecheck && bun run lint && bun run test && bun run smoke && bun run docs:checkbun run format); surface real ones. - Code review — run the
reviewskill over the diff. Address must-fix findings; note the rest. - Design review — if
packages/webchanged, run thedesign-reviewskill. - Docs & roadmap current — update
docs/06-roadmap.mdstatus the same change the work lands; docs product-agnostic; new behaviour has a test. - Commit — scoped, never
-A. Stage explicit paths (git add <path> …) so a concurrent session's files can't be swept in. Conventional message (feat:/fix:/docs:/chore:) explaining the behaviour change and how it was verified. End with theCo-Authored-Bytrailer. - PR — run the
prskill (push +gh pr create).
Report a one-line summary of each step's result.
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.
- 8d ago First seen · 27 lines · 60 tokens per session scan A 5a63357ec379
chores is a skill published in the GitHub repository ra3orblade/swarm (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 60 tokens to every session and 488 once invoked, about $0.0003 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 skills, from other repositories
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
pr-writer
Writes a pull-request description from the actual diff.
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions…
comprehensive-review-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.
batch-review
Review multiple related change sets for integration coherence and safe merge ordering.
create-pr
Create branch, atomic commits, push, and open a pull request with terse, exact messages. Conventional branch + commit format. PR title ≤70 chars, body says "why", not "what". Use when the user says "create pr", "create pullrequest", "create pull request", "make pr", "open pr", "open pullrequest", "open pull request"…