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 ccplugins/awesome-claude-code-plugins --skill setupgit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/setup)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/setup"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/setup.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.1 | $0.00090 | $0.11606 |
| Opus 5 | $0.00045 | $0.05803 |
| Sonnet 5 | $0.00018 | $0.02321 |
| Haiku 4.5 | $0.00009 | $0.01161 |
Grade A, and why
setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Step 3 — curl (Python 3.10+ not available):** Copies of this mod
1 near-identical copy found in the catalogue:
- setup — 94% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bedrock:setup — Vault Initialization
Plugin Paths
Templates and entity definitions are in the plugin directory, not in the vault root. Use the "Base directory for this skill" provided at invocation to resolve paths:
- Entity definitions:
<base_dir>/../../entities/ - Templates:
<base_dir>/../../templates/{type}/_template.md - Plugin CLAUDE.md:
<base_dir>/../../CLAUDE.md(auto-injected into context)
Where <base_dir> is the path shown in "Base directory for this skill".
Overview
This skill bootstraps any folder into a fully functional Bedrock-powered Obsidian vault through an interactive guided flow. It creates directories, copies templates, configures the vault, scaffolds example entities with bidirectional wikilinks, checks dependencies, and guides the user through next steps.
You are a setup agent. Follow the phases below in order. Do not skip steps.
Phase 0 — Idempotency Check
Check if the vault is already initialized:
ls .bedrock/config.json 2>/dev/null
If .bedrock/config.json exists:
-
Read and display the current configuration:
This vault is already initialized: - Language: <language> - Preset: <preset> - Domains: <domains> - Git strategy: <git.strategy or "commit-push" if absent> - Initialized at: <date> -
Check if this vault is registered in the global vault registry:
cat <base_dir>/../../vaults.json 2>/dev/nullIf the registry exists, check if any entry has a
pathmatching the current working directory.- If registered: display "Registered as vault
<name>" alongside the config above. - If NOT registered: display "This vault is not yet registered in the global vault registry."
- If registered: display "Registered as vault
-
Ask the user:
"This vault is already initialized. What would you like to do?"
- Reconfigure — Update language, domains, git strategy, and regenerate vault CLAUDE.md (directories and entities are NOT touched)
- Register only — Register this vault in the global registry (if not already registered) without changing configuration
- Skip — Exit with no changes
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 · 1,302 lines · 90 tokens per session scan A 7908765f8c8b
setup is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (932 stars, last pushed 25d ago), licensed Apache-2.0. It adds 90 tokens to every session and 11,606 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…