agentmods.dev

claude-code-plugins

A Claude Code settings file that configures a command to run when a session starts or resumes, along with environment values, enabled plugins, and worktree behavior.

In plain words
What is it for?
Use it to configure Claude Code startup actions, environment variables, enabled plugins, and the base reference used for worktrees.
Why use it?
It centralizes session and project automation settings so Claude Code can apply them consistently. The listed startup hook runs the project's cloud bootstrap script.

Settings file for Claude Code

12 yesterday A scan tokens not measured original MIT
View the source file melodic-software/claude-code-plugins
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.

agentmods
npx agentmods add settings/melodic-software/claude-code-plugins/settings
Clone the repo
git clone --depth 1 https://github.com/melodic-software/claude-code-plugins

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

claude-code-plugins 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.

.claude/settings.json · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "$schema": "https://json.schemastore.org/claude-code-settings.json",
  "autoMemoryEnabled": false,
  "env": {
    "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "1",
    "HOOK_TELEMETRY_SINK": ".claude/hooks/hook-telemetry-sink.sh"
  },
  "hooks": {
    "SessionStart": [
      {
        "matcher": "startup|resume",
        "hooks": [
          {
            "type": "command",
            "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/cloud-bootstrap.sh\""
          }
        ]
      }
    ]
  },
  "worktree": {
    "baseRef": "head"
  },
  "enabledPlugins": {
    "actionlint@melodic-software": true,
    "adhd@melodic-software": true,
    "ai-briefing@melodic-software": true,
    "ai-slop@melodic-software": true,
    "architecture@melodic-software": true,
    "autonomy@melodic-software": true,
    "bash-format@melodic-software": true,
    "biome-format@melodic-software": true,
    "bugs@melodic-software": true,
    "claude-config@melodic-software": true,
    "claude-memory@melodic-software": true,
    "claude-ops@melodic-software": true,
    "code-tidying@melodic-software": true,
    "codebase-health@melodic-software": true,
    "computer-use@melodic-software": true,
    "context-budget@melodic-software": true,
    "context-guard@melodic-software": true,
    "context7@melodic-software": true,
    "coupling@melodic-software": true,
    "debugging@melodic-software": true,
    "desktop-notification@melodic-software": true,
    "discipline@melodic-software": true,
    "discovery@melodic-software": true,
    "disk-hygiene@melodic-software": true,
    "docs-hygiene@melodic-software": true,
    "domain-driven-design@melodic-software": true,
    "dometrain@melodic-software": true,
    "education@melodic-software": true,
    "eol-normalizer@melodic-software": true,
    "evals@melodic-software": true,
    "event-storming@melodic-software": true,
    "firecrawl@melodic-software": true,
    "github@melodic-software": true,
    "go-format@melodic-software": true,
    "guardrails@melodic-

Read the full file on GitHub · 107 lines

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 · 107 lines scan A 6b4bed7f65a0

Subscribe to this mod's changes

claude-code-plugins is a settings file published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed yesterday), 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.

Git and workflowagentsai-toolsclaude-codemarketplacemcpplugins
Related

Other settings, from other repositories

agentenv

Agent settings declaring 1 hook event (PostToolUse) and 20 allowed tools.

eduardoarantes/agentenv · not measured

ai-coding-tools

Agent settings declaring 2 hook events (PostToolUse, UserPromptSubmit).

shopwareLabs/ai-coding-tools · not measured

claude-plugins

Agent settings declaring 1 hook event (SessionStart).

tomoking2004/claude-plugins · not measured

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

claude-cookbooks

Agent settings declaring 2 hook events (SessionStart, PreToolUse).

anthropics/claude-cookbooks · not measured

claude-code-best-practice

Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.

shanraisshan/claude-code-best-practice · not measured