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/dev-tooling-setting-upnpx skills add shopwareLabs/ai-coding-tools --skill dev-tooling-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/dev-tooling-setting-up)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/dev-tooling-setting-up"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/dev-tooling-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 | $0.00160 | $0.01315 |
| Opus 5 | $0.00080 | $0.00658 |
| Sonnet 5 | $0.00032 | $0.00263 |
| Haiku 4.5 | $0.00016 | $0.00131 |
Grade A, and why
dev-tooling-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 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.
This is a copy
86% identical to chunkhound-integration-setting-up — 4 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 — 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.
- 4d ago First seen · 102 lines · 160 tokens per session scan A 7ed505cbd7b6
dev-tooling-setting-up is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (43 stars, last pushed today), licensed MIT. It adds 160 tokens to every session and 1,315 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to chunkhound-integration-setting-up, differing in 4 lines, and is treated as a copy.
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-permission-state
Report the Claude Code permission state actually in effect. Discovers every settings scope (managed policy, user-global, project, local, and the pre-v2.1.211 start-directory copy), merges them into the effective allow/ask/deny set with each rule's source and precedence mechanic named, and classifies which allow rules…
audit-native-overlap
Map native Claude Code surfaces (built-in CLI commands, bundled skills, plugin-backed built-ins, session-provided skills) against the current repo's plugin skills and agents, so a custom component never silently duplicates what Claude Code itself now ships. Bare invocation is a READ-ONLY report: overlap candidates…
audit-performance
Read-only slowness-diagnostic capture for a Claude Code installation. Run it AT THE MOMENT the machine or a session feels slow, before restarting or deleting anything. One timed engine pass captures the four suspects: CLI version (regression), retention-sweep health including the silent unparsable-settings pause…
audit-prompting-postures
Audit locally-owned instruction components (skill bodies, agent definitions, hook instruction text, output styles, CLAUDE.md and rules) for MISSING posture guidance the official prompting guide says their purpose needs: delegation criteria and caps, minimal-scope and anti-test-gaming guardrails…
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'.