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/add-emacs/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/add-emacs)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/add-emacs"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/add-emacs.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.00058 | $0.02337 |
| Opus 5 | $0.00029 | $0.01169 |
| Sonnet 5 | $0.00012 | $0.00467 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
add-emacs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "http://localhost:8766/api/messages?since=0" This is a copy
88% identical to add-emacs — 88 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Emacs Channel
This skill adds Emacs support to Breadbrich Engels, then walks through interactive setup. Works with Doom Emacs, Spacemacs, and vanilla Emacs 27.1+.
What you can do with this
- Ask while coding — open the chat buffer (
C-c n c/SPC N c), ask about a function or error without leaving Emacs - Code review — select a region and send it with
breadbrich-org-send; the response appears as a child heading inline in your org file - Meeting notes — send an org agenda entry; get a summary or action item list back as a child node
- Draft writing — send org prose; receive revisions or continuations in place
- Research capture — ask a question directly in your org notes; the answer lands exactly where you need it
- Schedule tasks — ask Breadbrich Engels to set a reminder or create a scheduled Breadbrich Engels task (e.g. "remind me tomorrow to review the PR")
Phase 1: Pre-flight
Check if already applied
Check if src/channels/emacs.ts exists:
test -f src/channels/emacs.ts && echo "already applied" || echo "not applied"
If it exists, skip to Phase 3 (Setup). The code changes are already in place.
Phase 2: Apply Code Changes
Ensure the upstream remote
git remote -v
If an upstream remote pointing to https://github.com/qwibitai/salem.git is missing,
add it:
git remote add upstream https://github.com/qwibitai/salem.git
Merge the skill branch
git fetch upstream skill/emacs
git merge upstream/skill/emacs
If there are merge conflicts on package-lock.json, resolve them by accepting the incoming
version and continuing:
git checkout --theirs package-lock.json
git add package-lock.json
git merge --continue
For any other conflict, read the conflicted file and reconcile both sides manually.
This adds:
src/channels/emacs.ts—EmacsBridgeChannelHTTP server (port 8766)src/channels/emacs.test.ts— unit testsemacs/breadbrich.el— Emacs Lisp package (breadbrich-chat,breadbrich-org-send)import './emacs.js'appended tosrc/channels/index.ts
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 · 289 lines · 58 tokens per session scan A 568ccd1c69b7
add-emacs is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 2,337 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 88% identical to add-emacs, differing in 88 lines, and is treated as a copy.
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…