Answer: Run `claude plugin validate` with the mod's directory (e.g., `claude plugin validate ./first-mod`) to check what Claude Code reads from the mod's files; it catches a misspelled event, a bad manifest, and a module Claude Code can't read. Also check the one line Claude Code writes naming your mod when it skips something, which appears in the transcript for hot-reloading sessions, the debug log (start with `claude --debug`) for other interactive sessions, or stderr for a `claude -p` run with `--plugin-dir`. Status: Confirmed Entry: tool/claude-code/troubleshooting/mod-does-nothing Revision: 5 Digest: sha256:2ede102e1821d9da (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:20Z Last changed: 2026-11-19T12:19:18Z (skip line location for claude -p with --plugin-dir: — → stderr) Last verified: 2026-11-20T12:23:55Z Next check: 2026-11-21T12:23:55Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of validation command | claude plugin validate ./first-mod | [1] | 2026-11-20 debug session command | claude --debug | [1] | 2026-11-20 what validation catches | a misspelled event, a bad manifest, and a module Claude Code can't read | [1] | 2026-11-20 skip line location for hot-reload sessions | a dim line in the transcript | [1] | 2026-11-20 skip line location for claude -p with --plugin-dir | stderr | [1] | 2026-11-20 Sources: [1] Anthropic. "Troubleshoot a mod". https://code.claude.com/docs/en/plugins/mods/troubleshoot.md Role: primary. Accessed: 2026-11-20T12:23:55Z Quote: "as in `claude plugin validate ./first-mod`" (Supports: validation command) Quote: "start the session with `claude --debug`" (Supports: debug session command) Quote: "It catches a misspelled event, a bad manifest, and a module Claude Code can't read, without starting a session." (Supports: what validation catches) Quote: "**A session that hot-reloads a plugin directory**: a dim line in the transcript." (Supports: skip line location for hot-reload sessions) Quote: "**A `claude -p` run with `--plugin-dir`**: stderr, in the default text output format." (Supports: skip line location for claude -p with --plugin-dir) Published: 2026-11-20T03:00:59Z Snapshot SHA-256: 782ac923e4f73ee0bdb3a5512852310618c2666d6655dc230d953b5a543c12a4 (captured 2026-11-19T12:19:18Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:19:18Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:23:55Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:23:55Z Last attempt: 2026-11-20T12:23:55Z Notes and limitations: Extracted automatically from a single official source (section "Find out why a mod does nothing"). Related: https://latestn.com/tool/claude-code/troubleshooting/no-repositories-after-github Why do no repositories appear after I connect GitHub to Claude Code? https://latestn.com/tool/claude-code/troubleshooting/oauth-login-wsl-ssh-containers How do I fix OAuth login failures in WSL2, SSH, or containers for Claude Code? https://latestn.com/tool/claude-code/troubleshooting/plugin-disabled-user-settings-still-loads Why does a Claude Code plugin that I disabled in user settings still load? https://latestn.com/tool/claude-code/troubleshooting/hosting-known-limitations What are the known limitations of hosting the Claude Code Agent SDK? https://latestn.com/tool/claude-code/troubleshooting/list-loaded-mods How can I see which mods a Claude Code session loaded? https://latestn.com/tool/claude-code/troubleshooting/missing-inline-comments Where can I find Claude Code review findings that aren't showing as inline comments? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:19:18Z | changed | skip line location for claude -p with --plugin-dir: — → stderr | [1] 2026-11-19T12:19:18Z | changed | skip line location for hot-reload sessions: — → a dim line in the transcript | [1] 2026-11-19T12:19:18Z | changed | debug session command: — → claude --debug | [1] 2026-11-19T12:19:18Z | changed | debug log command: claude --debug → — | [1] 2026-11-19T12:19:18Z | changed | example command: claude plugin validate ./first-mod → — | [1] 2026-11-19T12:19:18Z | changed | validation command: claude plugin validate → claude plugin validate ./first-mod | [1] 2026-11-18T12:19:07Z | changed | what validation catches: — → a misspelled event, a bad manifest, and a module Claude Code can't read | [1] 2026-11-15T12:24:11Z | changed | debug log command: — → claude --debug | [1] 2026-11-15T12:24:11Z | changed | debug session command: claude --debug → — | [1] 2026-11-15T12:24:11Z | changed | what it catches: a misspelled event, a bad manifest, and a module Claude Code can't read → — | [1] 2026-11-14T12:19:44Z | changed | debug session command: — → claude --debug | [1] 2026-11-14T12:19:44Z | changed | what it catches: — → a misspelled event, a bad manifest, and a module Claude Code can't read | [1] 2026-11-14T12:19:44Z | changed | example command: — → claude plugin validate ./first-mod | [1] 2026-11-14T12:19:44Z | changed | validation command: — → claude plugin validate | [1] 2026-11-14T12:19:44Z | changed | Debug log command: claude --debug → — | [1] 2026-11-14T12:19:44Z | changed | What validation catches: a misspelled event, a bad manifest, and a module Claude Code can't read → — | [1] 2026-11-14T12:19:44Z | changed | Example command: claude plugin validate ./first-mod → — | [1] 2026-11-14T12:19:44Z | changed | Validation command: claude plugin validate → — | [1] 2026-11-13T03:05:20Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/troubleshooting/mod-does-nothing/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/troubleshooting/mod-does-nothing POST: https://latestn.com/dispute/tool/claude-code/troubleshooting/mod-does-nothing with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/troubleshooting/mod-does-nothing?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I find out why a Claude Code mod does nothing? Revision 5, last verified 2026-11-20T12:23:55Z. https://latestn.com/tool/claude-code/troubleshooting/mod-does-nothing (accessed 2026-11-21T09:53:45Z). @misc{LatestN_tool_claude_code_troubleshooting_mod_does_nothing_r5, title = {How do I find out why a Claude Code mod does nothing?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/troubleshooting/mod-does-nothing}}, note = {Revision 5; digest sha256:2ede102e1821d9da; last verified 2026-11-20T12:23:55Z; accessed 2026-11-21T09:53:45Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/troubleshooting/mod-does-nothing