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.
npx skills add dwmkerr/claude-toolkit --skill my-reposgit clone --depth 1 https://github.com/dwmkerr/claude-toolkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dwmkerr/claude-toolkit/my-repos)<a href="https://agentmods.dev/skills/dwmkerr/claude-toolkit/my-repos"><img src="https://agentmods.dev/badge/skills/dwmkerr/claude-toolkit/my-repos/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dwmkerr/claude-toolkit/my-repos"><img src="https://agentmods.dev/badge/skills/dwmkerr/claude-toolkit/my-repos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.00716 |
| Opus 5 | $0.00020 | $0.00358 |
| Sonnet 5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
my-repos 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 12d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Repos
Guide for locating and working with dwmkerr's repositories.
Repository Structure
~/repos/
├── github/
│ ├── dwmkerr/ # Personal repos (github.com/dwmkerr)
│ │ ├── effective-shell/
│ │ ├── hacker-laws/
│ │ ├── claude-toolkit/
│ │ └── ...
│ └── mckinsey/ # McKinsey open source repos (github.com/mckinsey)
│ └── ...
Finding a Repository
1. Check Local First
Always check if the repo exists locally:
ls ~/repos/github/dwmkerr/<repo-name>
ls ~/repos/github/mckinsey/<repo-name>
2. If Local Repo Exists
When working with an existing local repo:
-
Record the current state before making changes:
cd ~/repos/github/dwmkerr/<repo> ORIGINAL_BRANCH=$(git branch --show-current) git stash --include-untracked -
Fetch for reference if you need other branches:
git fetch origin git checkout origin/main # or any branch for reference -
Always return to original state when done:
git checkout "$ORIGINAL_BRANCH" git stash pop
3. If Repo Not Found Locally
Check if it exists on GitHub:
gh repo view dwmkerr/<repo-name> --json name,url
If it exists remotely, clone it:
git clone https://github.com/dwmkerr/<repo-name> ~/repos/github/dwmkerr/<repo-name>
For McKinsey repos:
gh repo view mckinsey/<repo-name> --json name,url
git clone https://github.com/mckinsey/<repo-name> ~/repos/github/mckinsey/<repo-name>
GitHub Details
- Personal GitHub username:
dwmkerr - Personal repos path:
~/repos/github/dwmkerr/ - McKinsey repos path:
~/repos/github/mckinsey/
Common Repos
Some frequently accessed repositories:
effective-shell- Book and website for shell/terminal skillshacker-laws- Laws, theories, and patterns for developersclaude-toolkit- Claude Code plugins and skillsdotfiles- Personal configuration files
Example Usage
User: "Check my repo effective-shell for the chapter on pipes"
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.
- 12d ago First seen · 106 lines · 41 tokens per session scan A 5eeb3d7033ce
my-repos is a skill published in the GitHub repository dwmkerr/claude-toolkit (23 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 716 once invoked, about $0.0002 per session on Opus 5. 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.
Other skills, from other repositories
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…