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 MicrotronX/mxLore --skill mxorchestrategit clone --depth 1 https://github.com/MicrotronX/mxLoreWrote 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/microtronx/mxlore/mxorchestrate)<a href="https://agentmods.dev/skills/microtronx/mxlore/mxorchestrate"><img src="https://agentmods.dev/badge/skills/microtronx/mxlore/mxorchestrate/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/microtronx/mxlore/mxorchestrate"><img src="https://agentmods.dev/badge/skills/microtronx/mxlore/mxorchestrate.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.00151 | $0.04318 |
| Opus 5.5 | $0.00060 | $0.01727 |
| Sonnet 5.5 | $0.00030 | $0.00864 |
| Haiku 4.5 | $0.00015 | $0.00432 |
Grade A, and why
mxOrchestrate 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 16d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
13 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.
- references/adhoc.md 861 B
- references/agent-spawn.md 1.2 KB
- references/auto-detect.md 1.1 KB
- references/hooks.md 2.0 KB
- references/init-session.md 3.6 KB
- references/model-tiering.md 2.5 KB
- references/output-discipline-findings.md 2.8 KB
- references/reconciliation.md 3.2 KB
- references/resume-enrichment.md 4.9 KB
- references/save-signal.md 3.5 KB
- references/state-schema.md 8.2 KB
- references/team-agents.md 875 B
- workflows.md 5.4 KB
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.
- 16d ago Changed 996dc8626550
- 23d ago Changed d8688013bd70
- 28d ago Changed 73261deaf459
- 29d ago Changed · -102 lines scan B → A c6ba05f1db21
- 1mo ago Changed · +1 lines d15f6e78947f
- 1mo ago Changed · +1 lines b63c6b9dca6c
- 1mo ago Changed · -3 lines da8b5ab6db97
- 1mo ago Changed · +2 lines c1a2fced4647
- 1mo ago First seen · 222 lines · 151 tokens per session scan B d3f088409143
mxOrchestrate is a skill published in the GitHub repository MicrotronX/mxLore (30 stars, last pushed yesterday), with no licence file. It adds 151 tokens to every session and 4,318 once invoked, about $0.0006 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-30.
Other skills, from other repositories
llm-wiki
Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings. Ingest sources into linked Markdown, answer questions with citations, lint or upgrade a wiki, and preserve useful synthesis across sessions and agents. Also capture verified task experience, consolidate…
raytsystem-save
Stage a cited synthesis as a typed raytsystem DRAFT bundle and escaped preview. Use for SAVE, preserving a verified query answer, preparing a knowledge proposal, or creating a reviewable draft; never treat SAVE as canonical promotion or publication.
pkm-explore
Use when researching what the vault knows about a topic — performs graph + semantic exploration with gap analysis to map existing knowledge and find missing connections. Primarily used via the vault-explorer agent. Not for routine session-start context loading (hooks handle that).
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…