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 agentmods add agents/rbbtsn0w/adg/claudegit clone --depth 1 https://github.com/RbBtSn0w/adgWrote 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/agents/rbbtsn0w/adg/claude)<a href="https://agentmods.dev/agents/rbbtsn0w/adg/claude"><img src="https://agentmods.dev/badge/agents/rbbtsn0w/adg/claude.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01235 |
| Opus 5 | $0.00000 | $0.00617 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
claude 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude (Anthropic) — Adapter Specification
Based on the Agent Adapter Template.
1. Official References
- Plugin docs: https://code.claude.com/docs/en/plugins-reference
- Standard plugin layout: https://code.claude.com/docs/en/plugins-reference#standard-plugin-layout
- File locations reference: https://code.claude.com/docs/en/plugins-reference#file-locations-reference
- Manifest schema: https://code.claude.com/docs/en/plugins-reference#plugin-manifest-schema
- Hooks reference: https://code.claude.com/docs/en/hooks
2. Projection Output
- Output directory:
.claude-plugin/ - Manifest file:
.claude-plugin/plugin.json - Adapter source:
src/adapters/anthropic.ts
3. Manifest Schema
Required fields: name
Optional fields: version, description, author, homepage, license,
category, skills, commands, agents, hooks, mcpServers, apps,
strict, displayName, repository, keywords, outputStyles,
lspServers, dependencies, userConfig, channels,
experimental.themes, experimental.monitors
// Minimal projected manifest
{
"name": "my-plugin",
"version": "1.0.0",
"description": "Example plugin",
"skills": "./skills/"
}
4. Supported Components
| Component | Supported | Manifest Key | Discovery Mechanism |
|---|---|---|---|
| Skills | ✅ | skills (string root or ./skills/<id> path array) |
Auto-scan skills/ dir for sub-dirs with SKILL.md; or explicit path array |
| Agents | ✅ | agents |
Markdown files in agents/ dir |
| Commands | ✅ | commands |
Markdown files in commands/ dir |
| Hooks | ✅ | hooks |
hooks/hooks.json (auto-loaded); explicit file path |
| MCP | ✅ | mcpServers |
.mcp.json or inline in manifest |
| Apps | ✅ | apps |
App directory |
| LSP | ✅ | lspServers |
.lsp.json or inline (Claude-only, not in ADG) |
| Monitors | ✅ | experimental.monitors |
monitors/monitors.json (Claude-only, not in ADG) |
| Themes | ✅ | experimental.themes |
themes/ dir (Claude-only, not in ADG) |
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 First seen · 114 lines · 0 tokens per session scan A cb580a274d45
claude is an agent published in the GitHub repository RbBtSn0w/adg (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,235 tokens. 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 agents, from other repositories
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
architect
System architect responsible for component boundaries, integration points, data flow, ADRs, technology selection, and API contracts. Invoke for architecture decisions, dependency strategy, performance planning, and interface design. Read-only — produces decisions and documentation.
sddp-devsetup
Analyzes the repository and guides the user through setting up their local development environment.
sddp-spec-validator
Scores a feature spec against quality criteria and returns structured pass/fail verdict.