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 thevibeworks/claude-code-docs --skill claude-automation-recommendergit 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/skills/thevibeworks/claude-code-docs/claude-automation-recommender)<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/claude-automation-recommender"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/claude-automation-recommender/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/thevibeworks/claude-code-docs/claude-automation-recommender"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/claude-automation-recommender.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.00077 | $0.02508 |
| Opus 5.5 | $0.00031 | $0.01003 |
| Sonnet 5.5 | $0.00015 | $0.00502 |
| Haiku 4.5 | $0.00008 | $0.00251 |
Grade A, and why
claude-automation-recommender 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 2mo 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 claude-automation-recommender — 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.
How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Automation Recommender
Analyze codebase patterns to recommend tailored Claude Code automations across all extensibility options.
This skill is read-only. It analyzes the codebase and outputs recommendations. It does NOT create or modify any files. Users implement the recommendations themselves or ask Claude separately to help build them.
Output Guidelines
- Recommend 1-2 of each type: Don't overwhelm - surface the top 1-2 most valuable automations per category
- If user asks for a specific type: Focus only on that type and provide more options (3-5 recommendations)
- Go beyond the reference lists: The reference files contain common patterns, but use web search to find recommendations specific to the codebase's tools, frameworks, and libraries
- Tell users they can ask for more: End by noting they can request more recommendations for any specific category
Automation Types Overview
| Type | Best For |
|---|---|
| Hooks | Automatic actions on tool events (format on save, lint, block edits) |
| Subagents | Specialized reviewers/analyzers that run in parallel |
| Skills | Packaged expertise, workflows, and repeatable tasks (invoked by Claude or user via /skill-name) |
| Plugins | Collections of skills that can be installed |
| MCP Servers | External tool integrations (databases, APIs, browsers, docs) |
Workflow
Phase 1: Codebase Analysis
Gather project context:
# Detect project type and tools
ls -la package.json pyproject.toml Cargo.toml go.mod pom.xml 2>/dev/null
cat package.json 2>/dev/null | head -50
# Check dependencies for MCP server recommendations
cat package.json 2>/dev/null | grep -E '"(react|vue|angular|next|express|fastapi|django|prisma|supabase|convex|stripe)"'
# Check for existing Claude Code config
ls -la .claude/ CLAUDE.md 2>/dev/null
# Analyze project structure
ls -la src/ app/ lib/ tests/ components/ pages/ api/ 2>/dev/null
Key Indicators to Capture:
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.
- 2mo ago First seen · 290 lines · 77 tokens per session scan A 441c57e26f09
claude-automation-recommender is a skill published in the GitHub repository thevibeworks/claude-code-docs (167 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 2,508 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to claude-automation-recommender, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
atlas-report
Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.
sync
Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.
atlas-map
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
validate
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
vibing-orchestrate
A coordinator for splitting independent tasks among separate vibing.nvim chats, a Neovim interface for working with coding agents, and combining their results.
adding-config-fields
Patterns for adding, renaming, removing, or retyping fields in DorkOS user config. Use when editing UserConfigSchema, MarketplacesFileSchema, or any conf-backed store — walks the Zod field → defaults → conf migration → docs → test lifecycle end-to-end.