DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build a custom Claude Code mod with Claude with Awesome Claude Code Mods

Ask Claude to build a mod, then test it locally with --plugin-dir before sharing it.

Authorization notice. Awesome Claude Code Mods is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer who wants a Claude Code interface change or behavior change that no existing mod provides.

The problemExisting mods do not cover a specific interface or behavior the developer needs.

The outcomeA local mod that runs in Claude Code and changes the interface or behavior the developer asked for.

What you need first

  • Claude Code 2.1.287 or later
  • Node 18 or later for mod-finder
  • A Claude Code terminal session
  • Access details reviewed for any mod before you install it

Steps

  1. Confirm you are on Claude Code 2.1.287 or later.
  2. Read Anthropic's guide, Getting started with Claude Code mods, for building and testing a mod.
  3. Ask Claude to build a mod, or install the mod-builder skill by karanb192 to plan, build and check it.
  4. Run claude --plugin-dir ./path/to/plugin to try the local plugin.
  5. Run /reload-plugins if the plugin needs to activate in an open session.

Prompt for your agent

Using the karanb192/awesome-claude-code-mods repo, build a local Claude Code mod for <task> at ./path/to/plugin. Expected output: a plugin folder that loads with `claude --plugin-dir ./path/to/plugin`. Verify that the plugin loads and that its behavior matches the task before sharing it.

Caveat. The README notes that validation checks source without running the mod, so you must test runtime behavior yourself.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page