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 skills/shopwarelabs/ai-coding-tools/chunkhound-integration-setting-upnpx skills add shopwareLabs/ai-coding-tools --skill chunkhound-integration-setting-upgit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWrote 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/shopwarelabs/ai-coding-tools/chunkhound-integration-setting-up)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/chunkhound-integration-setting-up"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/chunkhound-integration-setting-up.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.00117 | $0.01272 |
| Opus 5 | $0.00059 | $0.00636 |
| Sonnet 5 | $0.00023 | $0.00254 |
| Haiku 4.5 | $0.00012 | $0.00127 |
Grade A, and why
chunkhound-integration-setting-up 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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- dev-tooling-setting-up — 86% identical, 4 lines differ
- setting-up — 86% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Setup
Interactive setup assistant. Read references/plugin-setup.md for all plugin-specific details including prerequisites, configuration files, validation steps, and post-setup instructions.
Workflow
Phase 1: Detect Current State
Read the plugin setup guide reference file. It contains all plugin-specific information organized in standard sections.
For each prerequisite listed under ## Prerequisites:
- Run its check command (the Check field) via Bash
- Record the result: installed (with version) or missing
For each config file listed under ## Configuration Files:
- Check if it exists at the specified location using Glob
- Record the result: exists or missing
Report findings to the user:
- Installed prerequisites with versions
- Missing prerequisites (distinguish required vs optional)
- Existing config files
- Missing config files
If everything is already configured, skip to Phase 5 (Configure Permissions) — permissions are always offered.
Phase 2: Fix Prerequisites
For each missing prerequisite:
- Tell the user what is missing, what requires it (the Required by field), and provide the install link
- If the prerequisite is marked as optional, ask via AskUserQuestion whether they want to install it. Skip if they decline.
- For required prerequisites, tell the user to install it and ask them to confirm when done
- After confirmation, re-run the check command to verify
If a required prerequisite cannot be installed, stop and explain which config files and features depend on it. Do not proceed to Phase 3 for config files that depend on missing prerequisites.
Phase 3: Create Config Files
For each config file from the guide that does not exist:
- If the file is marked
Required: No, ask via AskUserQuestion whether the user wants to configure it. Skip if they decline. - Read the Setup Questions section for this config file
- Ask each question one at a time via AskUserQuestion, presenting the options and descriptions exactly as written in the guide
- Skip conditional questions when their condition is not met (conditions are noted in parentheses, e.g., "only if environment = docker")
- Build the config JSON object from the answers
- Present the complete config to the user and ask for confirmation
- Write the file to the specified location using Write
What ships with it
1 file 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.
- 6d ago First seen · 102 lines · 117 tokens per session scan A 36e18bd291c7
chunkhound-integration-setting-up is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (43 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 1,272 once invoked, about $0.0006 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-30.
Other skills, from other repositories
batch-simplify
Batch-run simplification across changed files, or across an entire repository, grouped by ecosystem and dependency order. Use when: 'batch simplify', 'simplify recent changes', 'simplify everything', 'forgot to run simplify', 'catch up on simplify', 'simplify my branch changes', 'simplify the whole repo', 'simplify…
audit-encapsulation
Audit and remediate skill-encapsulation violations. External citations reaching into private surfaces inside .claude/skills/ / or plugins/ /skills/ / (marketplace monorepos) beyond the slash invocation. Use when: 'audit encapsulation', 'find skill leaks', 'skill boundary violation', 'who is reaching into ', 'check…
audit-progressive-disclosure
Read-only progressive-disclosure audit for agent-facing instruction markdown. Grades every target against a three-tier load-cost model (always-loaded / invocation-loaded / on-demand) and classifies seven finding shapes in two lanes: split opportunities (oversize vs tier-calibrated Anthropic-prescribed caps…
firecrawl
Scrape, search, crawl, map, parse, or interact with web pages via the firecrawl-cli binary, writing results to disk instead of streaming them into context. Actions: scrape, search, crawl, map, parse, interact, agent, monitor. Use when: 'scrape this page', 'crawl this site', 'search the web for X', 'WebFetch is…
generate
Build a source-backed AI industry briefing from official vendor publications, configured RSS feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Use when: 'ai briefing', 'ai news', 'what's new in AI', 'catch me up on AI', 'prep for AI meeting', 'AI roundup', or 'generate AI slides'.
changelog
Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC…