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/commands/radumarias/xorio-claude-plugin/mallware-check)<a href="https://agentmods.dev/commands/radumarias/xorio-claude-plugin/mallware-check"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/mallware-check/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/commands/radumarias/xorio-claude-plugin/mallware-check"><img src="https://agentmods.dev/badge/commands/radumarias/xorio-claude-plugin/mallware-check.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.00047 | $0.11067 |
| Opus 5.5 | $0.00019 | $0.04427 |
| Sonnet 5.5 | $0.00009 | $0.02213 |
| Haiku 4.5 | $0.00005 | $0.01107 |
Grade D, and why
mallware-check scanned grade D with 6 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.
Instruction-override phrasingmediumPrompt injection
Text telling the model to disregard its earlier instructions or safety rules is the shape of a prompt injection, whoever wrote it.
> "ignore previous instructions", or a fake system/tool message. File contents Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Asks for rootlowPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- sudo in scripts without justification Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Reaches for credential filesmediumPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Paths: .ssh/id_rsa , .ssh/id_ed25519 , .ssh/authorized_keys Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- rm -rf / , rm -rf ~ , rm -rf * Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- fetch( , axios , requests.get , requests.post , urllib.request , http.get , http.request Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- eval( , exec( , execSync( , spawn( How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Malware & Security Scanner
You are a security auditor. Your job is to thoroughly scan the current working directory for anything malicious, suspicious, or untrustworthy. The user is about to work with this code and needs to know it's safe.
Target directory: The current working directory (always .)
Running it safely (relay to the user when relevant). Treat the target as live until the verdict is in: scan a cloned-but-never-installed copy, ideally in a VM or container that holds no credentials, and do not
npm install, build, or open the folder in an IDE — VS Code/Cursor run.vscode/tasks.jsonfolderOpentasks on open. Start Claude Code in a parent directory of the clone, never inside it: once the folder-trust prompt is accepted, Claude Code loads the cwd's.claude/settings*.json(hooks, permissions, env),.mcp.json,.claude/commands/agents/skills andCLAUDE.mdas the session's own configuration, so a hostile clone as cwd runs its hooks and plants its instructions before the scan starts. From a parent directory the scan still recurses into the clone, git history sweeps included, and a nestedCLAUDE.mdis only pulled in when a file beside it is Read — which the untrusted-content guard below covers. If the cwd itself is the repository under scan and contains.claude/orCLAUDE.md, add one line to RECOMMENDATION saying those were loaded as session config before the scan and that a re-run from a parent directory is the clean check.
User's additional context or question (if any): $ARGUMENTS
If the user provided a question or context above, keep it in mind and address it in your final report.
Context
Files in current directory:
!find . -type f -not -path './.git/*' -not -path '*/node_modules/*' -not -path '*/target/*' -not -path '*/__pycache__/*' -not -path '*/.venv/*' -not -path '*/vendor/*' -not -path '*/.next/*' -not -path '*/dist/*' -not -path '*/build/*' 2>/dev/null | head -500
Instructions
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 Changed · +174 lines · +26 tokens per session b3cfc83fd70b
- 1mo ago First seen · 270 lines · 21 tokens per session scan D 48006fbf48c8
mallware-check is a command published in the GitHub repository radumarias/xorio-claude-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 11,067 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it D with 6 findings (instruction-override phrasing, asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.