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 agentmods add skills/krmcbride/claude-plugins/code-examplesnpx skills add krmcbride/claude-plugins --skill code-examplesgit clone --depth 1 https://github.com/krmcbride/claude-pluginsWhat 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 | $0.00040 | $0.00491 |
| Opus 5 | $0.00020 | $0.00246 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
code-examples scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://grep.app/api/search?q={query}&page=1" | jq '.hits.hits[:5]' What it actually says
Code Examples
Find real-world code examples across millions of public GitHub repositories using grep.app.
When to activate:
- User wants to see real-world code examples
- User asks "how do others implement X?"
- User wants to find usage patterns for a library/API
- User needs production code examples (not docs)
API endpoint:
curl -s "https://grep.app/api/search?q={query}&page=1" | jq '.hits.hits[:5]'
Parameters:
| Parameter | Description |
|---|---|
q |
Search query (required) |
page |
Page number for pagination |
regexp |
true for regex search |
case |
true for case-sensitive |
f.lang |
Language filter (capitalized, e.g., TypeScript, Go, Python) |
f.repo.pattern |
Filter by repository pattern |
f.path.pattern |
Filter by file path pattern |
Examples:
Search for useEffect usage in TypeScript:
curl -s "https://grep.app/api/search?q=useEffect&f.lang=TypeScript&page=1" | jq '.hits.hits[:3]'
Search for Go error handling patterns:
curl -s "https://grep.app/api/search?q=if%20err%20!=%20nil&f.lang=Go&page=1" | jq '.hits.hits[:3]'
Search within a specific repo:
curl -s "https://grep.app/api/search?q=createContext&f.repo.pattern=facebook/react&page=1" | jq '.hits.hits[:3]'
Response format:
hits.hits[]- Array of search results- Each hit contains:
repo.raw(repo name),path.raw(file path),content.snippet(code snippet)
Note: Returns max 1000 results. For documentation, use the documentation-lookup skill instead.
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.
- yesterday First seen · 61 lines · 40 tokens per session scan A 3929aabdc6d9
code-examples is a skill published in the GitHub repository krmcbride/claude-plugins (3 stars, last pushed 8mo ago), licensed MIT. It adds 40 tokens to every session and 491 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…