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 AVIDS2/memorix --skill memorix-orchestrategit clone --depth 1 https://github.com/AVIDS2/memorixWrote 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/avids2/memorix/memorix-orchestrate)<a href="https://agentmods.dev/skills/avids2/memorix/memorix-orchestrate"><img src="https://agentmods.dev/badge/skills/avids2/memorix/memorix-orchestrate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00390 |
| Opus 5 | $0.00018 | $0.00195 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
memorix-orchestrate 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 8d 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.
What it actually says
Memorix Orchestrate
Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
The standard setup uses the lite MCP profile. Coordination MCP tools are exposed only by team or full; use the CLI fallback for ordinary installations, or explicitly start the server with --mode team. Do not probe unavailable team tools in a loop.
Tool Router
| Situation | Prefer | CLI fallback |
|---|---|---|
| Run managed subagent execution | CLI | memorix orchestrate --goal "<goal>" --agents claude:1,codex:1 |
| Register coordination identity | team_manage action join |
memorix team join --agentType <agent> |
| Create or inspect tasks | team_task |
`memorix task create |
| Send or read coordination messages | team_message |
`memorix message send |
| Share structured handoff | memorix_handoff |
memorix handoff send |
| Avoid file conflicts | team_file_lock |
`memorix lock lock |
| Poll joined coordination state | memorix_poll |
memorix poll |
Boundaries
- For ordinary memory, do not join coordination state.
- For production multi-agent execution, prefer
memorix orchestrateso the main process owns planning, dispatch, retries, and verification gates. - In worker prompts, use the worker agent ID returned by session start or team join; never use the coordinator ID as the worker identity.
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.
- 8d ago First seen · 29 lines · 37 tokens per session scan A 7484e0eadddd
memorix-orchestrate is a skill published in the GitHub repository AVIDS2/memorix (738 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 390 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-30.
Other skills, from other repositories
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
sdd-verify
Skill "sdd-verify" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, activation contract, hard rules and decision gates.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.