Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jhlee0409/claude-plugins/plugin install oasWrote 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/lint)<a href="https://agentmods.dev/commands/jhlee0409/claude-plugins/lint"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/lint/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/lint"><img src="https://agentmods.dev/badge/commands/jhlee0409/claude-plugins/lint.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.00010 | $0.04751 |
| Opus 5.5 | $0.00004 | $0.01900 |
| Sonnet 5.5 | $0.00002 | $0.00950 |
| Haiku 4.5 | $0.00001 | $0.00475 |
Grade A, and why
lint 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 — 749 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Lint
Check OpenAPI spec and codebase for consistency. Finds inconsistencies in manually written specs/code.
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
Target Selection
/oas:lint → Check both spec + code (default)
/oas:lint --spec → Check OpenAPI spec only
/oas:lint --code → Check codebase only
Usage
# Full check (smart caching for spec)
/oas:lint
# Specific rule only
/oas:lint --rule=naming
/oas:lint --rule=response-structure
# Fix suggestions
/oas:lint --fix
# Force fetch spec (bypass cache)
/oas:lint --force
# Use cached spec only (offline)
/oas:lint --offline
Smart Caching
Use skill: cache-manager
When linting spec (--spec or default):
1. Check if spec changed (HEAD request / mtime)
2. If unchanged → Use cached spec
3. If changed → Fetch new spec, update cache
When linting code only (--code):
→ No spec fetch needed
Part 1: Spec Lint Rules (--spec)
1. response-key-consistency
Check list response key naming consistency:
⚠️ INCONSISTENT: List response keys vary
Found 4 different patterns:
"items" → 12 endpoints (48%)
"results" → 8 endpoints (32%)
"videos" → 3 endpoints (12%)
"projects" → 2 endpoints (8%)
Examples:
GET /shortform/videos → { videos: [...] }
GET /project/projects → { results: [...] }
GET /workspace/users → { items: [...] }
💡 Recommendation:
Standardize on "items" (most common)
Or use resource-specific names consistently
2. timestamp-naming
Timestamp field naming consistency:
⚠️ INCONSISTENT: Timestamp field naming varies
Found 3 patterns:
"created_at" → 15 schemas
"created" → 8 schemas
"createdAt" → 3 schemas (camelCase)
Examples:
UserProfile.created_at
Project.created
VideoClip.createdAt
💡 Recommendation:
Standardize on "created_at" (most common, follows snake_case)
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 · 749 lines · 10 tokens per session scan A 079bdb8db43f
lint is a command published in the GitHub repository jhlee0409/claude-plugins (4 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 4,751 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
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
ci-sentinel
Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
debug
Diagnose why a ComfyUI workflow failed.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.fetch
Load an existing GitHub issue into the bug workflow (the complement of bug.issue) and seed a triage draft.