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 check-upstreamgit 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/check-upstream)<a href="https://agentmods.dev/skills/pdugan20/claudelint/check-upstream"><img src="https://agentmods.dev/badge/skills/pdugan20/claudelint/check-upstream/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/pdugan20/claudelint/check-upstream"><img src="https://agentmods.dev/badge/skills/pdugan20/claudelint/check-upstream.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.00057 | $0.00873 |
| Opus 5 | $0.00028 | $0.00436 |
| Sonnet 5 | $0.00011 | $0.00175 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
check-upstream 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Upstream
Detects new Claude Code documentation surface and drift between the official docs and claudelint's schemas, then recommends concrete updates.
The deterministic half of this system runs in CI. This skill adds the judgment the scripts deliberately do not attempt: reading the prose diff and deciding what it means for claudelint.
Usage
Run this skill when asked to check for upstream changes, verify schemas are up to date, or find out what changed in Claude Code's documentation.
Step 1: Refresh the baseline
Run npm run upstream:refresh.
Watch for two things in the output:
[NEW PAGE] <slug> (NOT WATCHED ...)- a docs page appeared that claudelint does not watch. This is how a whole feature (such as plugin dependencies) arrives. Read the page and decide whether it belongs insrc/upstream/watchlist.ts.Extractor guard tripped- the extractor stopped finding facts on a page. Upstream changed format. Fix the extractor in scripts/upstream/extract.ts. Do NOT lowerminFactsto make it pass; that disables the detector.
Step 2: Read the prose diff
Run git diff -- docs-baseline/.
This step is not optional, and it is not a skim. The scripts catch exactly two things: new pages, and hook-event drift. They do NOT catch field-level drift - a new, renamed, or removed field in any schema is caught ONLY by a human or agent reading this diff. They also cannot catch a constraint stated only in prose, and that class of change causes real bugs: the mintlify-docs install failure came from one sentence, "a bare string with only the plugin name".
So read the diff for both - changed fields and changed sentences. For each meaningful change, ask: does claudelint model this? Could a user violate it and have us report success?
Step 3: Run the conformance check
Run npm run check:upstream.
Its conformance findings cover hook events ONLY. A clean run means the HookEvents enum
matches the baseline - it says nothing about whether any other field is up to date. Field
drift is caught only by Step 2.
What ships with it
1 file 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.
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.
- 9d ago First seen · 84 lines · 57 tokens per session scan A e1c2345bd546
check-upstream is a skill published in the GitHub repository pdugan20/claudelint (12 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 873 once invoked, about $0.0003 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.