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 vnbochkarev-netizen/ViBo-memory --skill vibo-orchestratorgit clone --depth 1 https://github.com/vnbochkarev-netizen/ViBo-memoryWrote 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/vnbochkarev-netizen/vibo-memory/vibo-orchestrator)<a href="https://agentmods.dev/skills/vnbochkarev-netizen/vibo-memory/vibo-orchestrator"><img src="https://agentmods.dev/badge/skills/vnbochkarev-netizen/vibo-memory/vibo-orchestrator/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/vnbochkarev-netizen/vibo-memory/vibo-orchestrator"><img src="https://agentmods.dev/badge/skills/vnbochkarev-netizen/vibo-memory/vibo-orchestrator.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.00038 | $0.00759 |
| Opus 5 | $0.00019 | $0.00380 |
| Sonnet 5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
vibo-orchestrator 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤝 ViBo Orchestrator — Team Memory for agent teams
One memory for your whole agent team. Your agents write into a shared namespace; the orchestrator reads one compact context block — no re-asking, no duplicates, no forgotten decisions.
Measured on a 3-agent team: the orchestrator gets 3 facts instead of 3 full conversation histories (up to 96% fewer tokens per handoff).
Why orchestrators need it
| Without ViBo | With ViBo Orchestrator |
|---|---|
| Each agent forgets everything between sessions | Team remembers collectively (shared namespace) |
| Orchestrator re-asks or dumps full histories | One context summary — 3 facts, not megabytes |
| No way to tell who wrote what | --by author on every fact |
| Stale metrics pile up forever | --ttl — metrics expire automatically |
Quick test — 30 seconds
bash test_orchestra.sh
You will see: 3 agents write to team:demo → the orchestrator reads one
summary → personal facts stay private → metrics expire by TTL.
Install
- Copy the skill folder to your agent's skills directory (or unpack
vibo_orchestrator_1.0.0.zip). - Requires Python 3.11.
- Activate with your ViBo key (trial keys are free for 2 days by email):
python3.11 activate.py
Commands
# An agent writes to the shared team namespace
python3.11 vibo_use.py add "agent-1" "disk 48G free" --namespace team:demo --by sys-agent --ttl 6h
# The orchestrator reads ONE summary for the whole team
python3.11 vibo_use.py context --namespace team:demo
# → # ViBo shared context «team:demo»: 3 facts
# → • [sys-agent] agent-1: disk 48G free
# Private facts never leak to the team (no --namespace = personal)
python3.11 vibo_use.py add "personal" "my secret"
# Metrics expire automatically
python3.11 vibo_use.py add "metric" "load 0.1" --namespace team:demo --by sys-agent --ttl 3s
Limits (trial)
- Free trial (2 days, by email): up to 50 facts, up to 2 team namespaces.
- Full access: one license, $5/month — everything included (memory, web savings, archives, privacy, team memory). Get your key at https://wwwvibo.com.
What ships with it
7 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.
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.
- 11d ago First seen · 87 lines · 38 tokens per session scan A 781a11375b40
vibo-orchestrator is a skill published in the GitHub repository vnbochkarev-netizen/ViBo-memory (1 stars, last pushed 10d ago), licensed MIT. It adds 38 tokens to every session and 759 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
knowledge_store_skill
Skill for working with local .knowledge.yaml files via KnowledgeStore. Use this when you need to recall, search, or manage directory-local memories and knowledge links stored in plain YAML alongside the user's project files. KnowledgeStore is directory-scoped. Each directory that contains a .knowledge.yaml file…
cocoscout
Relevance-ranked context loading — Tier 2 async subagent (Haiku, <5s) that fires after Tier 1 deterministic checks in UserPromptSubmit. Injects ranked context from CocoGrove, CocoContext, Environment Inspector, Prompt Studio, and CocoDream.
cocohealth
Context utilization monitor — background monitor that samples context window utilization via PostToolUse hook, surfaces advisory at 60% and critical warning with recovery decision matrix at 70%.
pod-resume
Reconstruct context for a returning developer. Reads .cocoplus/ state and generates a narrative summary of project status, last achievements, pending tasks, recent decisions, available patterns, CocoCupper insights, and recommended next action.
pull-search
CocoPull session archive search — full-text search across past sessions. Handles $pull search " " with --since and --feature filters, and $pull index rebuild.
pod-kb
Display the project knowledge base (lifecycle/kb.md) — project-specific patterns, decisions, and gotchas accumulated by CocoCupper across sessions.