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 pdugan20/claudelint --skill optimize-cc-mdgit clone --depth 1 https://github.com/pdugan20/claudelintWrote 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/pdugan20/claudelint/optimize-cc-md)<a href="https://agentmods.dev/skills/pdugan20/claudelint/optimize-cc-md"><img src="https://agentmods.dev/badge/skills/pdugan20/claudelint/optimize-cc-md.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 44 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 183 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 211 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00077 | $0.02728 |
| Opus 5 | $0.00039 | $0.01364 |
| Sonnet 5 | $0.00015 | $0.00546 |
| Haiku 4.5 | $0.00008 | $0.00273 |
Grade A, and why
optimize-cc-md 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 8d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize CLAUDE.md
An interactive skill that helps you optimize your CLAUDE.md file through a 3-phase workflow: validate, assess quality, then make guided improvements. Each phase builds on the previous one so the user understands what's wrong, why it matters, and what to do about it.
Usage
Invoke with /optimize-cc-md or say "optimize my CLAUDE.md". Optionally pass a path: /optimize-cc-md CLAUDE.md. The skill guides you through three phases: validation, quality assessment, and guided improvement.
If a specific path is provided, optimize that file: $ARGUMENTS
Workflow Overview
Phase A: Validate Phase B: Assess Quality Phase C: Guided Improvement
───────────────── ─────────────────────── ───────────────────────────
Run claudelint → Explain issues plainly → Ask user what to fix
Read CLAUDE.md → Check quality criteria → Make surgical changes
Collect violations → Identify opportunities → Create @import files
→ Verify results
Phase A: Validate
Run automated validation and read the file to understand its current state.
Step 1: Run Validation
Use the Bash tool to run claudelint validation with verbose output:
npx claude-code-lint validate-claude-md --verbose
This identifies all CLAUDE.md issues including:
- File size violations (30KB warning, 50KB error)
- Missing or circular @imports
- Organization problems
- Invalid frontmatter in .claude/rules/ files
- Glob pattern issues
Step 2: Read the CLAUDE.md File
Use the Read tool to examine the user's CLAUDE.md:
Read(file_path: "CLAUDE.md")
Understand the current structure, content, and patterns. Note:
- Total file size and number of sections
- Which sections are project-specific vs generic
- Existing @import structure (if any)
- Content that could be scoped with globs
Phase B: Assess Quality
Go beyond automated checks. Explain issues conversationally and evaluate quality using criteria that linting can't catch.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHANGELOG.md 546 B
- optimize-cc-md.sh 871 B runs code
- references/common-fixes.md 1.8 KB
- references/file-type-taxonomy.md 6.3 KB
- references/import-patterns.md 9.1 KB
- references/organization-guide.md 8.1 KB
- references/quality-criteria.md 3.6 KB
- references/size-optimization.md 6.8 KB
- references/templates.md 6.7 KB
- references/troubleshooting.md 3.5 KB
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.
- 8d ago First seen · 317 lines · 77 tokens per session scan A 36d0103b5f4f
optimize-cc-md is a skill published in the GitHub repository pdugan20/claudelint (12 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 2,728 once invoked, about $0.0004 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
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
ship-safe-red-team
Run a multi-agent red team scan — 29 specialized security agents scan for 80+ attack classes including injection, auth bypass, SSRF, supply chain, Supabase RLS, MCP security, agentic AI, RAG poisoning, PII compliance, and more. Use when the user wants a deep security analysis beyond just secrets.
video-production
Produce programmable videos with Remotion using scene planning, asset orchestration, and validation gates for automated, brand-consistent video content.