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 skills add S3YED/appie-kit --skill brain-syncgit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/s3yed/appie-kit/brain-sync)<a href="https://agentmods.dev/skills/s3yed/appie-kit/brain-sync"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/brain-sync/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/s3yed/appie-kit/brain-sync"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/brain-sync.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.01305 |
| Opus 5.5 | $0.00034 | $0.00522 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (12 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,305 once invoked, about $0.0003 per session on Opus 5.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
memory-team
Guided setup for sharing moflo's durable learnings through a git-tracked artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up…
memory-worktree
Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my…
catchup
Restore context after /clear by summarizing recent work and project state.
brain
Search and analyze governed notes, decisions, runbooks, and conventions, returning a qmd:// citation for every supported claim. Use when checking what the brain has captured about architecture, infrastructure, decisions, or operating practices. Trigger with "/brain", "ask the brain", or "check my knowledge base".
pre-compact
Pre-compaction housekeeping. Walks a checklist (persistent memory updates, git hygiene, trash cleanup) plus an open-judgment audit, produces an SBAR with a go/no-go recommendation, and emits a copy-pasteable resume prompt for the post-compaction agent if work remains. Run this immediately before /compact.
hyperfocus-recovery
Reconstruct context after a deep session or interruption from git diff, modified files, and recent commits, then propose the next concrete action. Use when the user says "what was I doing", "where did I leave off", "lost my place", or invokes /hyperfocus-recovery.