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 mirkobozzetto/arsenal --skill issuegit clone --depth 1 https://github.com/mirkobozzetto/arsenalWrote 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/mirkobozzetto/arsenal/issue)<a href="https://agentmods.dev/skills/mirkobozzetto/arsenal/issue"><img src="https://agentmods.dev/badge/skills/mirkobozzetto/arsenal/issue/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/mirkobozzetto/arsenal/issue"><img src="https://agentmods.dev/badge/skills/mirkobozzetto/arsenal/issue.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.00020 | $0.01183 |
| Opus 5.5 | $0.00008 | $0.00473 |
| Sonnet 5.5 | $0.00004 | $0.00237 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue memory
Read the specific issue and comments before updating it; outside the duplicate check, do not query unrelated issues. Capture the problem, evidence, attempts, remaining action and verification so the issue can be resumed cold. Use references/issue-template.md when creating one.
Tracker
Read the project's CLAUDE.md first (AGENTS.md in harnesses that read that
instead). A line naming Linear, such as Issue tracker: Linear, team <name>,
selects Linear. Otherwise use GitHub through the authenticated gh CLI,
unchanged. Label, priority, project, parent and template follow that file
when it names them; never guess one.
Linear goes through the Linear MCP server already connected, whatever its
tool prefix: list_issues, get_issue, save_issue, list_comments,
save_comment. Without those tools, stop: create nothing on GitHub instead,
and give the setup. In Claude Code:
claude mcp add --transport http linear-server https://mcp.linear.app/mcp,
then /mcp to sign in; elsewhere, the client's Linear connector or MCP
setup with that URL.
Commands
Before create and from-tasks, search the open issues with the topic's
key words: gh issue list --search "<words>" --state open, or on Linear
list_issues with query and the team, ignoring completed and canceled
ones. Show a close match first, with the offer to add to it (update)
instead of creating a new one. Nothing is created without confirmation.
Confirm before creating or closing an issue. Preserve the Pickup Directive contract. No code changes, commits or agents.
On GitHub, append requested progress as comments instead of overwriting the
body. Label new issues arsenal; keep claude-memory on the ones that
already carry it and match either when listing or resuming.
On Linear, create is save_issue with title, team, the template as
description and the fields the CLAUDE.md names. update keeps one
progress comment per issue: find it with list_comments (it starts with
## Progress), rewrite it with save_comment and its id, and create it
only when none exists. resume reads get_issue and list_comments.
list returns the team's open issues, narrowed by the label or project the
CLAUDE.md names.
What ships with it
1 file 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.
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.
- 14d ago Changed · +37 lines · +2 tokens per session 67670ff2cb52
- 1mo ago Changed · +5 lines d8407ae3d51b
- 1mo ago Changed · +23 lines 8427a8a7b815
- 1mo ago Changed · +7 lines 39022cef0d26
- 1mo ago Changed · -58 lines · -99 tokens per session aa9fd3dc3748
- 2mo ago First seen · 89 lines · 117 tokens per session scan A 9d0f87d3d27e
issue is a skill published in the GitHub repository mirkobozzetto/arsenal (24 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,183 once invoked, about $0.0001 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
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
work-with-pr
Full PR lifecycle in a fresh task-owned git worktree: implement via the ulw-loop skill with mandatory evidence-bound manual QA → reviewer-readable English PR → verification loop (CI + Cubic, where Cubic is skipped only when its quota is exhausted) → merge by default → worktree cleanup. Decomposes one task into the…
lcx-contribute-bug-fix
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. LazyCodex-owned defects get a fork PR against code-yeongyu/oh-my-openagent (base dev, source-tree paths under packages/omo-codex/plugin, with the changelog fragment); upstream Codex bugs get a fork…
git-master
MUST USE for ANY git operations: atomic commits, rebase/squash/fixup, and history search (blame, bisect, log -S, reflog). Load it before running git yourself, or pass loadskills=['git-master'] to the task that commits. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.