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.
git clone --depth 1 https://github.com/jhlee0409/claude-pluginsWrote 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/commands/jhlee0409/claude-plugins/diff)<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/diff"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/diff/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/commands/jhlee0409/claude-plugins/diff"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/diff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00007 | $0.02376 |
| Opus 5.5 | $0.00003 | $0.00950 |
| Sonnet 5.5 | $0.00001 | $0.00475 |
| Haiku 4.5 | $0.00001 | $0.00238 |
Grade A, and why
diff 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 1mo 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Diff
Compare OpenAPI spec changes to see what's new, changed, or removed.
MCP Dependency Check
Before executing this command, invoke skill: mcp-dependency
- Verify OpenAPI Sync MCP server is installed
- If not available, offer to install via
npm install -g @jhlee0409/openapi-sync-mcp - Only proceed after MCP is confirmed available
Usage
# Current spec vs latest remote spec (smart caching)
/oas:diff --remote
# Compare two files
/oas:diff ./old-openapi.json ./new-openapi.json
# Current spec vs specific file
/oas:diff ./previous-version.json
# Compare with cached previous version
/oas:diff
# Force fetch remote (bypass cache)
/oas:diff --remote --force
# Use cached spec only (offline)
/oas:diff --offline
Smart Caching
Use skill: cache-manager
When using --remote:
1. Check if spec changed (HEAD request)
- ETag/Last-Modified comparison
2. If unchanged → Use cached spec for "new" side
3. If changed → Fetch new spec, update cache
Benefits:
- Fast when spec hasn't changed
- Saves bandwidth
- Always accurate when changes detected
Output with cache hit:
/oas:diff --remote
✅ Using cached spec (ETag unchanged)
Comparing cached version vs codebase...
Output with cache miss:
/oas:diff --remote
🔄 Spec changed, fetching updates...
Comparing new spec vs codebase...
Diff Process
┌─────────────────┐ ┌─────────────────┐
│ OLD SPEC │ │ NEW SPEC │
│ (cache/file) │ │ (remote/file) │
└────────┬────────┘ └────────┬────────┘
│ │
└──────────┬───────────┘
│
▼
┌─────────────────────┐
│ Compare Endpoints │
│ path + method │
└──────────┬──────────┘
│
┌───────────────┼───────────────┐
▼ ▼ ▼
┌───────┐ ┌──────────┐ ┌─────────┐
│ ADDED │ │ CHANGED │ │ REMOVED │
│ (+) │ │ (~) │ │ (-) │
└───┬───┘ └────┬─────┘ └────┬────┘
│ │ │
└──────────────┼───────────────┘
▼
┌─────────────────────┐
│ Output Report │
└─────────────────────┘
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.
- 1mo ago First seen · 371 lines · 7 tokens per session scan A 82233c5a14be
diff is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 9mo ago), licensed MIT. It adds 7 tokens to every session and 2,376 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
db-auth
A deployment command for connecting a web app to Neon, a hosted PostgreSQL database, and Clerk, a service for user sign-in and account management.
design
A command that creates a draft system architecture, an OpenAPI document describing web-service endpoints, and a data model from prepared product requirements and work plans.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.