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 agentmods add skills/breadchaincoop/labor.fun/redeploy-breadbrichnpx skills add BreadchainCoop/labor.fun --skill redeploy-breadbrichgit clone --depth 1 https://github.com/BreadchainCoop/labor.funWhat 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 | $0.00046 | $0.00861 |
| Opus 5 | $0.00023 | $0.00430 |
| Sonnet 5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
redeploy-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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/redeploy-breadbrich — Trigger Redeployment
Trigger a Breadbrich Engels redeployment on the droplet. This skill follows the push → merge → deploy rule — it only deploys code already merged to main on GitHub.
Who Can Use This
Any allowlisted user. Unknown senders are denied — respond with:
Redeployments require an allowlisted user. If you don't see yourself in
context/people/, ask someone who is already allowlisted to add you.
Pre-Flight Checks
Before triggering a deploy, verify:
- Identity: Confirm the requester resolves to a KB person
- Clean state: Ask if there are any uncommitted changes or open PRs that should be merged first
- Reason: Log why the redeployment is being triggered
How to Deploy
The deployment runs on the configured droplet (set DROPLET_HOST in .env). The standard flow:
# Option 1: From a machine with SSH access to the droplet
ssh "$DROPLET_HOST" "su - breadbrich -c '/opt/breadbrich-backups/safe-deploy.sh'"
# Option 2: From local checkout (Mac)
cd ~/Documents/Code/Claude/breadbrich && ./scripts/deploy.sh
What safe-deploy.sh Does
- Takes a pre-deploy backup snapshot
- Pulls latest from GitHub main
- Rsyncs code (preserving stateful paths:
.env,store/,data/,groups/,kb-ui/users.json) - Runs
npm install(if deps changed) - Runs
npm run build - Rebuilds container if
container/sources changed - Restarts
breadbrich.service - Health check (24s timeout)
- Automatic rollback on any failure
From Inside a Container (IPC)
If triggered from inside a Breadbrich Engels container (no direct SSH), create an IPC task:
echo '{"type": "redeploy", "reason": "Triggered by <requester>", "timestamp": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' > /workspace/ipc/tasks/redeploy_$(date +%s).json
Note: IPC-based redeployment requires the orchestrator to have a handler for
type: "redeploy". If this handler doesn't exist yet, the requester needs SSH access to the droplet.
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.
- 2d ago First seen · 88 lines · 46 tokens per session scan A f1e7f1145322
redeploy-breadbrich is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 861 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…