claudemods

All Claude Code modsDimeDataCloud/claude-modder

modder

A Claude Code mod in DimeDataCloud/claude-modder

One orchestrator over every Claude Code session you have open, with Jev (TypeSafe System One) deciding which one needs you

modder reaches L3 (network) by its classified calls and passed claude plugin validate on Claude Code 2.1.302.

Install hint

/plugin install modder --marketplace DimeDataCloud/claude-modder

From the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.

Access

L3 Uses the networkother: $.prompt.read, other: $.state.get, other: $.state.set, network, writes files, changes config, drives Claude, writes the prompt box, reads files, reads env vars, reads the transcript, persists state, draws

Validation

Passed on Claude Code 2.1.302

View the source on GitHub Back to the list

What the scan recorded

Observed events
every tool call, mcp__modder__skin calls, mcp__modder__mind calls
Hooks
session.start, session.end, turn.start, turn.complete, session.measure, tool.call, tool.check, command.run {command=modder}, command.run {command=skin}, tool.call {tool=mcp__modder__skin}, tool.call {tool=mcp__modder__mind}, ui.render {component=UserMessage|AssistantMessage|ToolUse|ToolResult|ToolGroup|ToolProgress|Spinner|InfoNotice|TurnDuration|CommandOutput|AskUserQuestion|PromptHint}, ui.render {component=SessionMode}, ui.render {component=AbovePrompt}, ui.render {component=Pane, requestId=modder}
API calls
$.clock.every, $.clock.now, $.clock.sleep, $.command.register, $.config.list, $.config.set, $.env.get, $.fs.list, $.fs.read, $.fs.write, $.http.fetch, $.model.complete, $.prompt.fill, $.prompt.read, $.session.id, $.session.messages, $.session.model, $.session.repo, $.session.root, $.state.get, $.state.set, $.store.get, $.store.set, $.tool.register, $.ui.close, $.ui.open, $.ui.resolve, $.ui.toast
Validation on 2.1.302
Passed
Scanned revision
d6d9f59d8880
Marketplace passed
claude-modder

These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.

Badge for your README

Reach badge for modder Validation badge for modder

Authors can show the latest scan result in their README. Each badge links to this page.

[![reach](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/DimeDataCloud--claude-modder--modder-reach.svg)](https://mods.aidojo.si/mods/DimeDataCloud--claude-modder--modder/)
[![validates](https://raw.githubusercontent.com/karanb192/awesome-claude-code-mods/main/badges/DimeDataCloud--claude-modder--modder-validates.svg)](https://mods.aidojo.si/mods/DimeDataCloud--claude-modder--modder/)