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 OutThisLife/brooklyn-skills --skill workgit clone --depth 1 https://github.com/OutThisLife/brooklyn-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/outthislife/brooklyn-skills/work)<a href="https://agentmods.dev/skills/outthislife/brooklyn-skills/work"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/work/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/outthislife/brooklyn-skills/work"><img src="https://agentmods.dev/badge/skills/outthislife/brooklyn-skills/work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.01511 |
| Opus 5.5 | $0.00018 | $0.00604 |
| Sonnet 5.5 | $0.00009 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
work 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 14d 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.
/work
/work [slug] is a declaration for this task: "spin up a dedicated worktree and
do the work there." It applies to what the user is starting right now — it is
not a standing rule that all work always happens in worktrees.
When invoked:
- Look at what the repo already does, and copy it.
- Create the worktree + branch and
cdinto it. - Do the requested work there.
Work aimed at an issue ("if it's open and reproducible")
Do these in order before writing any fix:
- Load the repo's own gate skill first. If the repo has a deployment or
brain skill (a
<prefix>-reposkill, a triage/claim system), load it before searching. Its per-issue gates (claim, overlap check, side-effect screen, risk title, auto-merge classifier) apply to a single/workfix as much as to a sweep. Skipping them because the request said "/work" rather than "triage" is the failure: the PR ships without the risk and side-effect sections she expects, and can duplicate her own open PR. - Find the issue. Search open and closed issues with several phrasings
(
gh issue list --state all --search "<q>"), plusin:titlevariants. A closed issue with a close-by-PR may already cover it. Check that before you call a newer report a duplicate. - Look for a PR that already fixes it. Search with
gh pr list --state all --search "<issue#>"and with keywords. Drafts count: a contributor can park a finished fix as a draft because of an open-PR cap. If a complete fix exists, salvage it (cherry-pick the commit so authorship is kept) instead of writing a parallel one. Check her own open PRs too (gh pr list --author @me --state open --json number,title,files,mergeable,autoMergeRequest), not only contributors': an armed-but-CONFLICTING PR of hers on the same function is live work. Fold both into ONE combined PR that supersedes them (cherry-pick what applies, port the rest by hand onto main's current file layout, keep everyCo-authored-by), then disarm (gh pr merge N --disable-auto) and close the sources with a comment linking the replacement. - Prove it red on the base. Apply only the tests first
(
gh pr diff <N> > f.diff && git apply --include='tests/*' f.diff), run them, and see them fail. Then remove the file andgit cherry-pickthe real commit, so the test file isn't left as an untracked conflict. - Reproduce the user-visible path end to end. Run it on a detached base worktree and on the branch, and keep both outputs as before/after evidence for the PR body.
- Re-run any failures on the base worktree before calling them unrelated. "Fails identically on untouched base" is the claim to report.
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.
- 14d ago Changed · +40 lines 40725066ae19
- 1mo ago Changed · +11 lines dc8e451e347d
- 1mo ago Changed · +4 lines 986b3f03e162
- 2mo ago First seen · 59 lines · 45 tokens per session scan A 9362edbeadac
work is a skill published in the GitHub repository OutThisLife/brooklyn-skills (209 stars, last pushed 8d ago), licensed MIT. It adds 45 tokens to every session and 1,511 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-30.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…