agentmods.dev

plugin-setup

An interactive setup package for plugins that include a SETUP.md file, with setup guidance for dev-tooling, gh-tooling, and chunkhound-integration.

In plain words
What is it for?
Setting up those three supported plugin areas. The input does not describe any other setup targets.
Why use it?
It helps configure supported plugins by following their setup instructions interactively instead of working out the required steps alone.

Plugin for Claude Code

42 4d ago A scan tokens not measured original MIT
View the source file shopwareLabs/ai-coding-tools
Install

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.

Claude Code
/plugin marketplace add shopwareLabs/ai-coding-tools
agentmods
npx agentmods add plugins/shopwarelabs/ai-coding-tools/plugin-setup
Clone the repo
git clone --depth 1 https://github.com/shopwareLabs/ai-coding-tools

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

plugin-setup 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 yesterday.

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.

plugins/plugin-setup/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "name": "plugin-setup",
  "version": "1.0.2",
  "description": "Interactive setup skills for plugins that ship a SETUP.md. Bundles one setting-up skill per supported plugin: dev-tooling, gh-tooling, and chunkhound-integration.",
  "author": {
    "name": "Shopware Labs"
  },
  "license": "MIT",
  "keywords": ["setup", "configuration", "dev-tooling", "gh-tooling", "chunkhound"],
  "homepage": "https://github.com/shopwareLabs/ai-coding-tools/tree/main/plugins/plugin-setup",
  "repository": "https://github.com/shopwareLabs/ai-coding-tools"
}
Changes

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.

  1. yesterday First seen · 13 lines scan A 5bda0de9fe18

Subscribe to this mod's changes

plugin-setup is a plugin published in the GitHub repository shopwareLabs/ai-coding-tools (42 stars, last pushed 4d ago), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code reviewProductivityanthropicclaudeclaude-codemarketplacepluginsshopware
Related

Other plugins, from other repositories

claude-ops

Claude Code operations toolkit. Twelve skills: audit-skill-visibility (audit whether each installed skill is actually VISIBLE to the model, and diagnose why most of a fleet never gets used — a skill is invisible when its description is dropped by Claude Code's skill-listing context budget, which drops descriptions…

melodic-software/claude-code-plugins · not measured

autonomy

Governed autonomous agent operation: role-topology, binding-seam, wiring-vs-advisor, telemetry, return-accounting, trigger-dispatch, per-work-class guardrail-matrix, standing-routine-catalog, and design-only runner-charter contracts for climbing the AI-adoption ladder, plus a guided-setup skill that discovers an…

melodic-software/claude-code-plugins · not measured

context-guard

Per-session context-window observability plus the first shipped consumer: a statusline wrapper tees each session's contextwindow fields to a per-session snapshot file, a zone resolver classifies usage into smart/acceptable/dumb bands (percentage bands plus window-class token bands, conservative-min combination, zones.

melodic-software/claude-code-plugins · not measured

claude-config

Nine configuration-health skills (plus setup) for a repo's Claude Code configuration: audit (settings.json / .mcp.json / hooks / plugins / permissions drift), audit-automation-gaps (evidence-gated verdicts on automation gaps), audit-permission-grants (allow-rule / allowed-tools grants for auto-mode durability and…

melodic-software/claude-code-plugins · not measured

ai-briefing

Build source-backed AI-industry briefings from official vendor publications, configured RSS/Atom feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Deduplicate, rank, and present results as markdown or optional HTML/PPTX decks, with repository-owned profile, audience, and brand…

melodic-software/claude-code-plugins · not measured

context-budget

Measure a Claude Code session's fixed startup context payload per item, on the consumer's machine at a pinned, version-stamped binary — including per-tool attribution of the built-in tool pools that /context reports only as lump sums, derived live by A/B bare-name-deny differencing with enforced comparability rules…

melodic-software/claude-code-plugins · not measured