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.
/plugin marketplace add mirkobozzetto/arsenalnpx agentmods add plugins/mirkobozzetto/arsenal/issuegit clone --depth 1 https://github.com/mirkobozzetto/arsenalGrade A, and why
issue 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 3d 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": "issue",
"version": "1.0.0",
"description": "Use GitHub issues as cross-session resolution memory. Create, update, and resume self-contained, cold-readable issues via the gh CLI, recording the hypothesis and the resolution.",
"author": {
"name": "Mirko Bozzetto",
"url": "https://github.com/mirkobozzetto"
},
"license": "MIT",
"homepage": "https://github.com/mirkobozzetto/arsenal/tree/main/plugins/issue"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 117 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 12 lines scan A 56810421a95e
issue is a plugin published in the GitHub repository mirkobozzetto/arsenal (14 stars, last pushed 9d 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-30.
Other plugins, from other repositories
tdmcp marketplace
Plugin marketplace listing 1 plugin: tdmcp.
uizze
Build product-specific UI with the free anti-ui-slop skill and optional focused UIZZE references.
taskmaster marketplace
Plugin marketplace listing 1 plugin: taskmaster.
harness-maker
Per-project AI coding harness for Claude Code · Cursor · Codex. Profiler + 10-dim interview build a different harness for every project.
skillet
Summon anyone's public skills by handle, or route a task to the best skill in your own kit.
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.