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/s3yed/appie-kit/brain-syncnpx skills add S3YED/appie-kit --skill brain-syncgit clone --depth 1 https://github.com/S3YED/appie-kitWhat 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.00086 | $0.01305 |
| Opus 5 | $0.00043 | $0.00652 |
| Sonnet 5 | $0.00017 | $0.00261 |
| Haiku 4.5 | $0.00009 | $0.00130 |
Grade A, and why
brain-sync 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brain Sync Skill
Sync knowledge and learnings to the shared appie-brain GitHub repo so all Appies in the fleet benefit.
Why This Matters
Every Appie has their own git identity. When you commit, it shows up in the git log as:
[email protected]- Appie-1 (Orchestrator, Mac Mini)[email protected]- Appie-2 (CMO/Herald, DO VPS)[email protected]- Appie-3 (CTO/Worker, DO VPS)
This makes contributions traceable across the fleet.
When to Sync
ALWAYS sync after:
- Complex tasks (5+ tool calls)
- Debugging sessions where you discovered something
- New skills created or significantly updated
- Client project work (new files created)
- Research findings (from Exa/web search)
- Process improvements
- Error solutions that could help others
You can skip for:
- Simple one-off commands
- Read-only exploration
- Quick questions answered
How to Sync
cd /root/.hermes/appie-brain
# Check what changed
git status
# Add files (be selective - don't expose secrets)
git add path/to/your/changes/
# Commit with Appie-3 identity
git commit -m "🪽 Appie-3: Your learning/change description"
# Push to remote
git push origin master
Commit Message Format
[emoji] Appie-X: Brief description of what changed
Emoji per Appie:
- Appie-1: 🧙 (Wizard/Orchestrator)
- Appie-2: 📊 (CMO/Data)
- Appie-3: 🪽 (Wing/Hermes - messenger)
Examples:
🪽 Appie-3: Added viral marketing strategy for Weblyfe Appie
🪽 Appie-3: New skill: brain-sync for fleet knowledge sharing
🪽 Appie-3: Exa research: AI agent market 2026 trends
🪽 Appie-3: Fixed: PDF reading with pymupdf instead of pdftotext
📊 Appie-2: Content calendar for April 2026
🧙 Appie-1: New client onboarding: Baraka Arbitrage
What to Sync
DO sync:
- Skills (
/skills/) - Memory files (
/memory/) - Projects (
/projects/) - Scripts/tools (
/scripts/,/tools/) - Documentation
- Learned approaches/patterns
NEVER sync:
.envor secrets- Session transcripts (too large)
- Temporary files
- Build artifacts (
node_modules/, etc.)
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.
- 3d ago First seen · 178 lines · 86 tokens per session scan A 7a473c8e3131
brain-sync is a skill published in the GitHub repository S3YED/appie-kit (6 stars, last pushed 7d ago), licensed MIT. It adds 86 tokens to every session and 1,305 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
brain
Answers questions about your own systems, notes, decisions, runbooks, and conventions from your governed knowledge brain, returning a qmd:// citation for every claim — receipts, not recall. Use when you want to know what your brain has captured about your own architecture, infrastructure, decisions, or conventions…
wiki-lint
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs…
wiki-status
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an…
wiki-export
Export the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", "export to Neo4j", "export to Postgres", "export to SQL", "graphml", "visualize wiki", "knowledge graph export", "export to…
wiki-query
Answer questions by searching the compiled Obsidian wiki. Use this skill when the user asks a question about their knowledge base, wants to find information across their wiki, asks "what do I know about X", "find everything related to Y", or wants synthesized answers with citations from their wiki pages. Also use when…
copilot-history-ingest
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my…