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 BreadchainCoop/labor.fun --skill peer-reviewsgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWrote 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/breadchaincoop/labor.fun/peer-reviews)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/peer-reviews"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/peer-reviews.svg" alt="Measured on agentmods" 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.00073 | $0.01619 |
| Opus 5 | $0.00036 | $0.00809 |
| Sonnet 5 | $0.00015 | $0.00324 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
peer-reviews 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 6d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quarterly peer reviews & self-evaluations
The peer-reviews flow (a profile plugin) DMs each member their quarterly
assignment — write a self-evaluation, and review two assigned peers — and
nudges until done. You are the receiving end: you help members complete and
file these, and you schedule the review meetings.
The quarter label looks like 2026-Q2 (the quarter being closed out). Take it
from the nudge message in the DM; if unsure, ask.
Filing a self-evaluation
Trigger: a member replies wanting to do their self-eval, or says "file my self-eval".
- Pull their last-quarter goals so they evaluate against what they set,
not from a blank page. Look in the shared KB (read-only at
/workspace/shared-kb/): the prior quarter's self-eval (peer-reviews/<prev-quarter>/self-eval/<slug>.md), their people file, and any goals/directivesdocs. If you genuinely can't find goals, say so and ask them to restate the goals they set. - Help them reflect: progress against each goal, what landed, what slipped, what they want next quarter. Keep their voice — don't rewrite it into corporate tone.
- File it via
modify_kb_file:- path:
peer-reviews/<QUARTER>/self-eval/<slug>.md - content: frontmatter (
author: <slug>,date: <ISO date>,quarter: <QUARTER>) then the self-evaluation.
- path:
- Confirm it's filed (the flow reads file existence to stop nudging).
Filing a peer review
Trigger: a member is writing one of their assigned peer reviews (the nudge told them whom — e.g. "a peer review of Marv"), or says "record my review of X".
- Resolve the reviewee to their KB slug (match against
/workspace/shared-kb/people/). - Help the reviewer write a fair, specific review of that peer's quarter.
- File it via
modify_kb_file:- path:
peer-reviews/<QUARTER>/reviews/<reviewer-slug>--<reviewee-slug>.md(double hyphen separates the two slugs — match it exactly; the flow keys completion off this filename). - content: frontmatter (
reviewer: <slug>,reviewee: <slug>,date: <ISO date>,quarter: <QUARTER>) then the review.
- path:
- Confirm filed. Two filed reviews of a member = their requirement met.
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.
- 6d ago First seen · 121 lines · 73 tokens per session scan A 6119bdd6042d
peer-reviews is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 1,619 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…