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/thevibeworks/claude-code-docsWrote 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/thevibeworks/claude-code-docs/cwc-makers)<a href="https://agentmods.dev/plugins/thevibeworks/claude-code-docs/cwc-makers"><img src="https://agentmods.dev/badge/plugins/thevibeworks/claude-code-docs/cwc-makers/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/thevibeworks/claude-code-docs/cwc-makers"><img src="https://agentmods.dev/badge/plugins/thevibeworks/claude-code-docs/cwc-makers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cwc-makers 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 1mo 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.
This is a copy
100% identical to cwc-makers — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "cwc-makers",
"version": "1.0.0",
"description": "Seamless onboarding for the Code-with-Claude Makers Cardputer: one /maker-setup command clones the build-with-claude repo, flashes UIFlow firmware, and installs the Claude Buddy app bundle onto a freshly-plugged-in M5Stack Cardputer-Adv.",
"author": {
"name": "Anthropic",
"email": "[email protected]"
},
"homepage": "https://claude.com/cwc-makers",
"repository": "https://github.com/moremas/build-with-claude",
"license": "Apache-2.0",
"keywords": [
"cardputer",
"m5stack",
"esp32",
"hardware",
"maker",
"onboarding",
"cwc"
]
}
What it installs
The manifest is a name and a version. 2 skills, 1 command travel with it, and installing the plugin installs all of them — 232 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 22 lines scan A daea51ab5138
cwc-makers is a plugin published in the GitHub repository thevibeworks/claude-code-docs (158 stars, last pushed today), 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. It is 100% identical to cwc-makers, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
arm-cortex-microcontrollers
ARM Cortex-M firmware development for Teensy, STM32, nRF52, and SAMD with peripheral drivers and memory safety patterns.
dgx-spark-ops
NVIDIA DGX Spark (GB10 Grace Blackwell) environment operations: aarch64/CUDA-13 stack setup, training gotcha preflights, and unified-memory/thermal management for local ML workloads.
vibing-nvim
Neovim MCP tools, skills, and subagents for vibing.nvim — lets Claude Code read/edit buffers, drive LSP, and manage windows in a running Neovim instance.
flow
The /flow engine — one unified, PM-agnostic workflow system spanning capture → done. Manual stages and an autonomous loop seated on DorkOS Pulse.
claude-docs
Searchable local index of Claude documentation. Provides the /docs command for instant access to API references, guides, and tutorials. Auto-discovery Skill reads docs automatically when you ask Claude-related questions. Docs auto-update via SessionStart hook.
uitkit-automation
Browser automation, Playwright, SaaS scaffolding, spec-to-repo generation, IoT, embedded systems, game dev, and office document automation.