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.
git clone --depth 1 https://github.com/radumarias/xorio-claude-pluginWrote 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/plugins/radumarias/xorio-claude-plugin/xorio-claude-plugin)<a href="https://agentmods.dev/plugins/radumarias/xorio-claude-plugin/xorio-claude-plugin"><img src="https://agentmods.dev/badge/plugins/radumarias/xorio-claude-plugin/xorio-claude-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
xorio 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 6d 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
{
"name": "xorio",
"version": "0.1.0",
"description": "xorio development toolkit — dev workflows, testing, cleanup, polish, review, security",
"author": {
"name": "Radu Marias",
"url": "https://github.com/radumarias"
},
"repository": "https://github.com/radumarias/xorio-claude-plugin",
"license": "MIT",
"keywords": ["development", "testing", "code-quality", "workflows"]
}
What it installs
The manifest is a name and a version. 9 skills, 10 commands, 4 agents, 2 hooks travel with it, and installing the plugin installs all of them — 1,398 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill team-forming A 185 tokens
- Skill brainstorm A 164 tokens
- Skill review-loop A 147 tokens
- Skill brainstorm-mythos A 119 tokens
- Skill cleanup-code A 66 tokens
- Skill generate-tests-coverage A 28 tokens
- Skill generate-tests-module A 30 tokens
- Skill polish A 70 tokens
- Skill review A 53 tokens
- Command guide A 14 tokens
- Command root-cause A 37 tokens
- Command polish A 16 tokens
- Command review-pr A 65 tokens
- Command review-pr-mythos A 74 tokens
- Command tests A 15 tokens
- Command commit-message A 4 tokens
- Command check-deps B 10 tokens
- Command review A 15 tokens
- Command mallware-check D 21 tokens
- Agent test-analyzer A 65 tokens
- Agent test-generator A 61 tokens
- Agent test-docs-advisor A 62 tokens
- Agent security-auditor A 77 tokens
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
What ships with it
1 file beside plugin.json 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.
- 6d ago First seen · 13 lines scan A a0f3d1f0a097
xorio is a plugin published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
code-review
Perform a comprehensive code review of recent changes.
double-check
Verify code correctness with systematic second-pass analysis.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…
unslop
Three anti-slop scanners in one bundle: a-unslop-text catches AI-diction and cadence tells in prose, a-unslop-code catches bugs and tutorial-shaped patterns in source, a-unslop-ui catches stock-default looks in web UI. Each ships a deterministic scanner plus a Build mode that heads off the tell before it ships. The…
tidy
Careful low-risk codebase cleanup across 7 focused tracks: deduplication, type consolidation, dead code removal, circular dependency untangling, type strengthening, error-handling cleanup, and deprecated/AI-slop removal. Each track inspects, writes a critical assessment, ranks proposed changes by confidence, and…