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 shopwareLabs/ai-coding-tools --skill dev-environment-bootstrappinggit 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-environment-bootstrapping)<a href="https://agentmods.dev/skills/shopwarelabs/ai-coding-tools/dev-environment-bootstrapping"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/dev-environment-bootstrapping/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/shopwarelabs/ai-coding-tools/dev-environment-bootstrapping"><img src="https://agentmods.dev/badge/skills/shopwarelabs/ai-coding-tools/dev-environment-bootstrapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 64 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 247 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 17 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00144 | $0.02876 |
| Opus 5.5 | $0.00058 | $0.01150 |
| Sonnet 5.5 | $0.00029 | $0.00575 |
| Haiku 4.5 | $0.00014 | $0.00288 |
Grade A, and why
dev-environment-bootstrapping 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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shopware Dev Environment Bootstrapping
Orchestrate the full first-run Shopware development environment setup. Detects current state, presents a numbered plan, confirms with the user, executes the plan via lifecycle MCP tools, then stops with a handoff message.
Output scope: Executes MCP lifecycle tools and Bash clone commands. Writes no config files. Invokes no dev-tooling skills. Stops after printing the handoff message.
Phase 1 — Detection (no user interaction)
Silently probe the working directory to determine what already exists and what is missing. Do not prompt the user during this phase.
Shopware Checkout State
- Check
composer.jsonexists and containsshopware/coreas a dependency — determines whether this is a Shopware project root. - Check
src/Core/directory exists — confirms a full Shopware source checkout vs. a vendor install. - Check
.envfile exists and containsDATABASE_URL— determines if the environment has been configured. - Check
var/cache/directory exists — rough indicator thatbin/console cache:clearhas run at least once.
Environment Clues
Check for these files/directories to infer the intended execution environment:
docker-compose.ymlordocker-compose.yaml— Docker Compose environment.ddev/config.yaml— DDEV environmentVagrantfile— Vagrant environment- None of the above — native environment assumed
Plugin State
- Check
custom/plugins/directory exists and list any subdirectories — these are already-present plugins. - Determine whether the user's stated intent (from their message) involves a specific plugin name.
Database State
.envwithDATABASE_URLpresent → database may be configuredvar/cache/present → system:install has likely run before
Dev Tooling Config
- Check for
.mcp-php-tooling.jsonin the project root — if present, environment args are already locked in and will be used by the lifecycle tools automatically. - Check for
.mcp-php-tooling.jsonin.claude/— same.
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.
- 14d ago Changed f091e60df2ab
- 1mo ago Changed 709c33423a10
- 1mo ago Changed 0bd274211e53
- 1mo ago First seen · 283 lines · 144 tokens per session scan A d88b74f2354f
dev-environment-bootstrapping is a skill published in the GitHub repository shopwareLabs/ai-coding-tools (45 stars, last pushed 3d ago), licensed MIT. It adds 144 tokens to every session and 2,876 once invoked, about $0.0006 per session on Opus 5.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
cs-channel-message
A channel-message writing tool for search ads, advertising, customer relationship messages, and app notifications. It uses the NCM sequence—Need, Channel, Moment, Message, and CTA—to adapt wording to where and when customers see it.
commerce-detail-page-copy
A writing tool for Korean e-commerce product detail pages. It can generate a full 13-section page, assess an existing page, or create two persona-based copy sets.
commerce-detail-page-planner
A strategy brief for deciding what a Korean e-commerce product page should say, show, and prioritise. It defines the main message, opening, page structure, sales channel approach, and photo checklist before copy, code, or images are made.
commerce-integrated-strategy
An e-commerce planning skill that combines customer research, product messaging, and store data into a one-page sales strategy with three priority actions.
commerce-ad-claim-compliance-kr
A pre-publication check for Korean advertising and product-page wording. It reviews claims against South Korea's advertising, food-safety, and e-commerce laws.
commerce-automation-audit
A planning and consulting tool for finding automation opportunities in an online store. It reviews work such as products, pricing, orders, stock, marketing, and business data, then proposes priorities and a phased roadmap.