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/x-integrationnpx skills add BreadchainCoop/labor.fun --skill x-integrationgit 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/x-integration)<a href="https://agentmods.dev/skills/breadchaincoop/labor.fun/x-integration"><img src="https://agentmods.dev/badge/skills/breadchaincoop/labor.fun/x-integration.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 | $0.00060 | $0.03050 |
| Opus 5 | $0.00030 | $0.01525 |
| Sonnet 5 | $0.00012 | $0.00610 |
| Haiku 4.5 | $0.00006 | $0.00305 |
Grade A, and why
x-integration 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 3d 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
86% identical to x-integration — 70 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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X (Twitter) Integration
Browser automation for X interactions via WhatsApp.
Compatibility: Breadbrich Engels v1.0.0. Directory structure may change in future versions.
Features
| Action | Tool | Description |
|---|---|---|
| Post | x_post |
Publish new tweets |
| Like | x_like |
Like any tweet |
| Reply | x_reply |
Reply to tweets |
| Retweet | x_retweet |
Retweet without comment |
| Quote | x_quote |
Quote tweet with comment |
Prerequisites
Before using this skill, ensure:
- Breadbrich Engels is installed and running - WhatsApp connected, service active
- Dependencies installed:
npm ls playwright dotenv-cli || npm install playwright dotenv-cli - CHROME_PATH configured in
.env(if Chrome is not at default location):# Find your Chrome path mdfind "kMDItemCFBundleIdentifier == 'com.google.Chrome'" 2>/dev/null | head -1 # Add to .env CHROME_PATH=/path/to/Google Chrome.app/Contents/MacOS/Google Chrome
Quick Start
# 1. Setup authentication (interactive)
npx dotenv -e .env -- npx tsx .claude/skills/x-integration/scripts/setup.ts
# Verify: data/x-auth.json should exist after successful login
# 2. Rebuild container to include skill
./container/build.sh
# Verify: Output shows "COPY .claude/skills/x-integration/agent.ts"
# 3. Rebuild host and restart service
npm run build
launchctl kickstart -k gui/$(id -u)/com.breadbrich # macOS
# Linux: systemctl --user restart breadbrich
# Verify: launchctl list | grep breadbrich (macOS) or systemctl --user status breadbrich (Linux)
Configuration
Environment Variables
| Variable | Default | Description |
|---|---|---|
CHROME_PATH |
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome |
Chrome executable path |
NANOCLAW_ROOT |
process.cwd() |
Project root directory |
LOG_LEVEL |
info |
Logging level (debug, info, warn, error) |
Set in .env file (loaded via dotenv-cli at runtime):
What ships with it
10 files 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.
- agent.ts 7.3 KB runs code
- host.ts 4.3 KB runs code
- lib/browser.ts 4.0 KB runs code
- lib/config.ts 1.5 KB runs code
- scripts/like.ts 1.6 KB runs code
- scripts/post.ts 2.2 KB runs code
- scripts/quote.ts 2.7 KB runs code
- scripts/reply.ts 2.5 KB runs code
- scripts/retweet.ts 2.0 KB runs code
- scripts/setup.ts 2.7 KB runs code
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.
- 3d ago First seen · 417 lines · 60 tokens per session scan A 03642537b7c0
x-integration is a skill published in the GitHub repository BreadchainCoop/labor.fun (2 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 3,050 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to x-integration, differing in 70 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.
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…