joshdavenport-mods
My Claude Code mods
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/joshdavenport--claude-mods)HTML
<a href="/listings/joshdavenport--claude-mods"><img src="/api/listings/joshdavenport--claude-mods/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Add the marketplace once, then install the mods you want. At the prompt of a terminal session:
/plugin marketplace add joshdavenport/claude-mods /plugin install clarity@joshdavenport-mods
Or from a shell, all of them:
claude plugin marketplace add joshdavenport/claude-mods for mod in clarity grill-q-prompt md-glow skill-augment skill-prompt-view; do claude plugin install "$mod@joshdavenport-mods" done
`claude plugin marketplace update joshdavenport-mods`, then `claude plugin update <mod>@joshdavenport-mods`, picks up a new release.
Hooks modules load only in a workspace whose trust dialog has been accepted. Each mod's README lists anything else it needs (clarity wants a Nerd Font, md-glow wants `glow` on your machine).
From a local checkout
To work on the mods, add the checkout itself as the marketplace instead of the GitHub repo:
git clone git@github.com:joshdavenport/claude-mods.git ~/Projects/claude-mods claude plugin marketplace add ~/Projects/claude-mods for mod in clarity grill-q-prompt md-glow skill-augment skill-prompt-view; do claude plugin install "$mod@joshdavenport-mods" done
Each mod is then read straight from `plugins/<mod>`: edit a file and run `/reload-plugins`, with no reinstall or version bump. Both sources register the marketplace as `joshdavenport-mods`, so use one or the other; `claude plugin marketplace remove joshdavenport-mods` clears the current one.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 37 lines
- {
- "name": "joshdavenport-mods",
- "owner": {
- "name": "Josh"
- },
- "metadata": {
- "description": "Josh's Claude Code mods",
- "version": "0.3.0"
- },
- "plugins": [
- {
- "name": "clarity",
- "source": "./plugins/clarity",
- "description": "Brings extra clarity to Claude's replies: status pills, labels with icons, distinct headings and a closing \"What I need from you\" section, drawn by its own markdown renderer"
- },
- {
- "name": "grill-q-prompt",
- "source": "./plugins/grill-q-prompt",
- "description": "When a reply asks a grilling round of numbered questions (❓ Q1, ❓ Q2, …), fills the empty prompt box with an answer template: one `qN. ` line per question."
- },
- {
- "name": "md-glow",
- "source": "./plugins/md-glow",
- "description": "Offers markdown files written in the session for viewing in a pane, rendered by the local glow CLI"
- },
- {
- "name": "skill-augment",
- "source": "./plugins/skill-augment",
- "description": "Augments the prompts of skills you can't edit: markdown files under ~/.claude/skills-augment and <project>/.claude/skills-augment name the skills they add to and whether their text goes at the start or end of the skill's prompt."
- },
- {
- "name": "skill-prompt-view",
- "source": "./plugins/skill-prompt-view",
- "description": "Shows each skill's expanded prompt inline in the transcript, as the model received it"
- }
- ]
- }
README.md · README · 61 lines
- # claude-mods
- A set of [Claude Code](https://claude.com/claude-code) mods: plugins built on function hooks that change how Claude Code looks and behaves. They live in one marketplace and share one version.
- | Mod | What it does |
- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
- | [clarity](plugins/clarity) | Brings extra clarity to Claude's replies: status pills, labels with icons, distinct headings and a closing "What I need from you" section, drawn by its own markdown renderer. |
- | [grill-q-prompt](plugins/grill-q-prompt) | When a reply asks a grilling round of numbered `❓ Q1`, `❓ Q2` questions, fills the empty prompt box with a `q1. `, `q2. ` answer template. |
- | [md-glow](plugins/md-glow) | Offers each markdown file written in the session for viewing in a pane, rendered by the local `glow` CLI. |
- | [skill-augment](plugins/skill-augment) | Adds your own markdown to the prompts of skills you can't edit, such as those shipped in plugins. |
- | [skill-prompt-view](plugins/skill-prompt-view) | Shows each skill's expanded prompt inline in the transcript, as the model received it. |
- ## Install
- Add the marketplace once, then install the mods you want. At the prompt of a terminal session:
- ```
- /plugin marketplace add joshdavenport/claude-mods
- /plugin install clarity@joshdavenport-mods
- ```
- Or from a shell, all of them:
- ```sh
- claude plugin marketplace add joshdavenport/claude-mods
- for mod in clarity grill-q-prompt md-glow skill-augment skill-prompt-view; do
- claude plugin install "$mod@joshdavenport-mods"
- done
- ```
- `claude plugin marketplace update joshdavenport-mods`, then `claude plugin update <mod>@joshdavenport-mods`, picks up a new release.
- Hooks modules load only in a workspace whose trust dialog has been accepted. Each mod's README lists anything else it needs (clarity wants a Nerd Font, md-glow wants `glow` on your machine).
- ### From a local checkout
- To work on the mods, add the checkout itself as the marketplace instead of the GitHub repo:
- ```sh
- git clone git@github.com:joshdavenport/claude-mods.git ~/Projects/claude-mods
- claude plugin marketplace add ~/Projects/claude-mods
- for mod in clarity grill-q-prompt md-glow skill-augment skill-prompt-view; do
- claude plugin install "$mod@joshdavenport-mods"
- done
- ```
- Each mod is then read straight from `plugins/<mod>`: edit a file and run `/reload-plugins`, with no reinstall or version bump. Both sources register the marketplace as `joshdavenport-mods`, so use one or the other; `claude plugin marketplace remove joshdavenport-mods` clears the current one.
- ## Develop
- ```sh
- pnpm install
- pnpm test # claude plugin test, for every mod
- pnpm lint # oxfmt check, oxlint, typecheck, claude plugin validate
- pnpm format # oxfmt
- pnpm showcase # regenerate docs/showcase/<mod>.png (all mods, or name some)
- ```
- `pnpm showcase` drives each mod in a real Claude Code session (Haiku) in a background [Rex](https://www.superlogical.com/rex) session, captures the terminal as HTML and screenshots it with headless Chrome. It needs Rex, Chrome, the JetBrainsMono Nerd Font and the mods installed from this checkout. Leave the `showcase-*` sessions unopened while it runs: opening one hands the terminal's size to the app. Scenarios live in `scripts/showcase/scenarios.ts`.
- `pnpm typecheck` needs `plugins/<mod>/.claude-plugin/types/`, which Claude Code writes when an interactive `claude --plugin-dir plugins/<mod>` session loads the mod. `CLAUDE.md` has the rules the engine and validator enforce, and how releases are versioned.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.