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/dravensoft-dev/arenaWrote 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/dravensoft-dev/arena/marketplace)<a href="https://agentmods.dev/plugins/dravensoft-dev/arena/marketplace"><img src="https://agentmods.dev/badge/plugins/dravensoft-dev/arena/marketplace/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/plugins/dravensoft-dev/arena/marketplace"><img src="https://agentmods.dev/badge/plugins/dravensoft-dev/arena/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dravensoft marketplace 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 4d 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": "dravensoft",
"owner": {
"name": "Dravensoft"
},
"description": "Dravensoft's official plugins for Claude Code.",
"plugins": [
{
"name": "arena",
"source": {
"source": "github",
"repo": "dravensoft-dev/arena",
"ref": "v13.0.0"
},
"description": "Arena, Dravensoft's design system, as an Agent Skill: design tokens, React and Angular primitives, a shared Tailwind layer, guidelines, and a style plugin any project can replace. It carries the design language and not the skin, so any project brings its own palette and fonts.",
"version": "13.0.0",
"author": {
"name": "Dravensoft"
},
"homepage": "https://arena.dravensoft.org",
"keywords": ["design-system", "design-tokens", "ui", "branding", "arena",
"react", "angular", "tailwindcss", "accessibility", "frontend"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 4d ago Changed 8c50210cd825
- 18d ago Changed 3f54db3a29e3
- 19d ago Changed db98719c2aef
- 20d ago Changed 2c07cb8012b9
- 1mo ago Changed b8d7ae6eba2e
- 1mo ago Changed 5e2d58fe0177
- 1mo ago Changed 004d23a717c7
- 1mo ago Changed fdfdea2f9228
- 1mo ago Changed 3adc57c1f8dd
- 2mo ago First seen · 26 lines scan A 432f8dc4b658
dravensoft marketplace is a plugin published in the GitHub repository dravensoft-dev/arena (2 stars, last pushed 4d 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
ccmux
Drive the ccmux cross-harness CLI to dispatch work to other AI coding agents (Claude Code, Codex, Cursor, OpenCode, Pi, Gemini) through programmatic ccmux invoke calls. Requires the ccmux CLI on PATH.
figma-console-mcp-skills
The full collection: design tokens (export/import/setup), variable and library management, component-set analysis and docs, WCAG and design-system linting, accessibility audits, version history, changelog, blame, comments, annotations, FigJam, and Slides.
sandy-cli
Sandy: sandboxed TypeScript execution for AWS queries via the sandy CLI.
sniff
Autonomous QA scanner via sniff-qa: walks your running app in a real browser and reports real bugs (broken pages/links, console/network errors, broken forms, state-loss, empty/placeholder data, bad loading/error states, responsive + a11y) with reproduction proof, severity, confidence, and a fix. No API key.
overlayqa
Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…