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 sssemil/SKILLS --skill brutal-workergit clone --depth 1 https://github.com/sssemil/SKILLSWrote 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/sssemil/skills/brutal-worker)<a href="https://agentmods.dev/skills/sssemil/skills/brutal-worker"><img src="https://agentmods.dev/badge/skills/sssemil/skills/brutal-worker/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/sssemil/skills/brutal-worker"><img src="https://agentmods.dev/badge/skills/sssemil/skills/brutal-worker.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.00054 | $0.01204 |
| Opus 5.5 | $0.00022 | $0.00482 |
| Sonnet 5.5 | $0.00011 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
brutal-worker 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 2mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brutal Worker
Complete one exact work item and its pull request. Never select a replacement.
Required Context
Always require the stable task reference and read applicable repository rules.
Read ../brutal-shared/integration-resolver.md and
../brutal-shared/support/contracts.md. Reuse a managed assignment’s validated
work-store/code-host identities, canonical local root, worktree, branch, and
base; resolve only missing data needed by the current phase.
For standalone work, also read
../brutal-swarm/references/parallel-execution.md, create or resume the isolated
worktree with ../brutal-swarm/scripts/worktree_manager.py, and read
../brutal-inf-fix-loop/SKILL.md plus its source skills.
For managed work, the immutable handoff establishes assignment identity; the phase snapshot supplies revalidated mutable state. Runtime names, logs, and old snapshots are observational and grant no provider authority. Read only the supplied phase context file.
Hard Rules
- Own only the handed-off item, branch, worktree, and pull request.
- Select only
taskorreview_finding; never implement a plan or investigation. - Never merge, approve, request changes, force-push, delete a remote branch, or create a second pull request for the item.
- Preserve unrelated changes and edit only the isolated worktree.
- Keep the item
in_progressuntil a fresh review has no CRITICAL or MAJOR. Then it may move toin_review; move it todoneonly after its PR merged.
Managed Phase Protocol
When the prompt contains a managed phase snapshot, do only that phase and return the supervisor’s exact result. Do not continue into the next phase.
work
Read the full item, history, parent/blockers, assignment, and existing PR link. Prove the exact claim from the expected state before changing code. Validate worktree, branch, base branch/SHA, and branch task marker. Implement, test, self-review, commit, push, and find-or-create the single marked PR. Return a checkpoint with current base/head, PR, verification, and zeroed review fields.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 114 lines · 54 tokens per session scan A 983768a35329
brutal-worker is a skill published in the GitHub repository sssemil/SKILLS (2 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 1,204 once invoked, about $0.0002 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 skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…