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 RealDougEubanks/ClaudeMarketplace --skill adrgit clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/adr)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/adr"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/adr/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/realdougeubanks/claudemarketplace/adr"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/adr.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.00039 | $0.01382 |
| Opus 5 | $0.00019 | $0.00691 |
| Sonnet 5 | $0.00008 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
adr 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 9d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adr
Purpose
Create, list, update, and supersede Architecture Decision Records (ADRs) following the Markdown Architectural Decision Records (MADR) format. Maintains an ADR directory (see Directory Convention below). Works standalone or as a companion to /architecture-design.
Directory Convention
Before creating anything, detect where this project keeps ADRs. Use Glob to check, in order: docs/decisions/ADR-*.md, docs/adr/*.md, adr/*.md, docs/architecture/decisions/*.md. Use the first directory that already contains ADRs. Only if none exists, default to docs/decisions/. All paths below refer to this detected directory.
ADR Format (MADR)
Every ADR uses this structure:
# ADR-NNN: <Title>
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-NNN
**Deciders:** <names or roles>
**Tags:** <architecture | security | database | api | infrastructure | ...>
## Context and Problem Statement
[1-3 paragraphs: what situation led to this decision? What is the problem being solved? What forces are at play?]
## Decision Drivers
- [driver 1: most important constraint or goal]
- [driver 2]
## Considered Options
1. **[Option A — Recommended]** — one-sentence description
2. **[Option B]** — one-sentence description
3. **[Option C]** — one-sentence description
## Decision Outcome
**Chosen option:** [Option A], because [one paragraph justification tied to decision drivers].
### Positive Consequences
- [what becomes easier, better, or possible]
### Negative Consequences / Trade-offs
- [what becomes harder, more expensive, or is given up]
## Pros and Cons of the Options
### Option A — [Name]
- ✅ [pro]
- ✅ [pro]
- ❌ [con]
- ❌ [con]
### Option B — [Name]
- ✅ [pro]
- ❌ [con]
## Links
- [Link to related ADR, design doc, RFC, or Jira ticket]
Instructions
Step 1 — Determine the action
Parse $ARGUMENTS first and dispatch directly — do not ask if the action is given:
| Invocation | Action |
|---|---|
/adr create <title> |
Step 2a, using <title> as the decision title |
/adr list |
Step 2b |
/adr update <n> <status> |
Step 2c on ADR-<n>, setting <status> |
/adr supersede <n> |
Step 2d replacing ADR-<n> |
/adr search <keyword> |
Step 2e with <keyword> |
What ships with it
3 files 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.
- 9d ago First seen · 160 lines · 39 tokens per session scan A 597b3e709858
adr is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 1,382 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
tools-unity-behavior-designer
Behavior Designer patterns for AI behavior trees including task creation, shared variables, conditionals, and debugging.
tools-unity-flowcanvas
FlowCanvas visual scripting patterns for abilities, custom nodes, and graph execution.
tools-unity-gameplay-ability-system
Gameplay Ability System patterns for abilities, effects, attributes, and tags including recursion safety and lifecycle management.
tools-unity-state-machine
State machine patterns for Unity including hierarchical states, async transitions, and cleanup safety.
eng-unity-mobile-optimization
Mobile-specific Unity optimization patterns for memory, battery, thermal, and performance.