Borrowing it
Nothing to install: this file belongs to BreadchainCoop/labor.fun. 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/BreadchainCoop/labor.fun/main/.claude/skills/update-nanoclaw/SKILL.mdgit 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/update-nanoclaw)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/update-nanoclaw"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/update-nanoclaw.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.00041 | $0.02827 |
| Opus 5 | $0.00020 | $0.01413 |
| Sonnet 5 | $0.00008 | $0.00565 |
| Haiku 4.5 | $0.00004 | $0.00283 |
Grade A, and why
update-breadbrich 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 7d 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.
This is a copy
84% identical to update-claudeclaw — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
About
Your labor.fun fork drifts from upstream as you customize it. This skill pulls upstream changes into your install without losing your modifications.
Run /update-breadbrich in Claude Code. You can pass the upstream repo URL as an argument: /update-breadbrich https://github.com/your-org/labor.fun.git.
How it works
Preflight: checks for clean working tree (git status --porcelain). Resolves the upstream repo URL — you can pass one as an argument; otherwise it uses the existing upstream remote, or asks you (default https://github.com/BreadchainCoop/labor.fun.git). If you pass a URL that differs from the current upstream, it offers to update the remote. Detects the upstream branch name (main or master).
Backup: creates a timestamped backup branch and tag (backup/pre-update-<hash>-<timestamp>, pre-update-<hash>-<timestamp>) before touching anything. Safe to run multiple times.
Preview: runs git log and git diff against the merge base to show upstream changes since your last sync. Groups changed files into categories:
- Skills (
.claude/skills/): unlikely to conflict unless you edited an upstream skill - Source (
src/): may conflict if you modified the same files - Build/config (
package.json,tsconfig*.json,container/): review needed
Update paths (you pick one):
merge(default):git merge upstream/<branch>. Resolves all conflicts in one pass.cherry-pick:git cherry-pick <hashes>. Pull in only the commits you want.rebase:git rebase upstream/<branch>. Linear history, but conflicts resolve per-commit.abort: just view the changelog, change nothing.
Conflict preview: before merging, runs a dry-run (git merge --no-commit --no-ff) to show which files would conflict. You can still abort at this point.
Conflict resolution: opens only conflicted files, resolves the conflict markers, keeps your local customizations intact.
Validation: runs npm run build and npm test.
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.
- 7d ago First seen · 248 lines · 41 tokens per session scan A 617b8e99c904
update-breadbrich is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 6d ago), licensed MIT. It adds 41 tokens to every session and 2,827 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to update-claudeclaw, differing in 44 lines, and is treated as a copy.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".