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/random6913/claude-code-superkit/lint-runnernpx skills add RaNDoM6913/claude-code-superkit --skill lint-runnergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWhat 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.00025 | $0.00885 |
| Opus 5 | $0.00013 | $0.00443 |
| Sonnet 5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
lint-runner 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint
Auto-detect the project's linters and run them.
Target
Parse the user's request to determine scope and parameters. Accepted formats: backend, frontend, all, --fix.
Step 1 — Detect Linters
Scan the project for stack markers and their associated linters:
| Marker | Format Command | Lint Command | Stack |
|---|---|---|---|
go.mod |
gofmt -w . |
go vet ./... |
Go |
go.mod + golangci-lint in PATH |
gofmt -w . |
golangci-lint run |
Go (extended) |
package.json + .eslintrc* / eslint.config.* |
— | npx eslint . |
ESLint |
package.json + tsconfig.json |
— | npx tsc --noEmit |
TypeScript |
package.json + prettier config |
npx prettier --write . |
npx prettier --check . |
Prettier |
pyproject.toml + [tool.ruff] |
ruff format . |
ruff check . |
Python (ruff) |
pyproject.toml + [tool.black] |
black . |
— | Python (black) |
pyproject.toml + [tool.flake8] / setup.cfg |
— | flake8 |
Python (flake8) |
pyproject.toml + [tool.mypy] |
— | mypy . |
Python (mypy) |
Cargo.toml |
cargo fmt |
cargo clippy -- -D warnings |
Rust |
Makefile with lint target |
— | make lint |
Makefile |
Makefile with fmt target |
make fmt |
— | Makefile |
If a Makefile with lint / fmt targets exists, prefer them — they may include project-specific setup.
Step 2 — Determine Scope
Based on the user's request:
backend
Lint backend code only. In a monorepo, cd into the backend directory first.
frontend
Lint frontend code only. In a monorepo, cd into the frontend directory first.
all (default if no argument)
Run all detected linters sequentially. Report results for each.
--fix
When --fix is present in the request, run linters in auto-fix mode:
- Go:
gofmt -w .(always fixes) - ESLint:
npx eslint . --fix - Prettier:
npx prettier --write . - ruff:
ruff check . --fix && ruff format . - black:
black .(always fixes) - Rust:
cargo fmt+cargo clippy --fix --allow-dirty
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.
- 2d ago First seen · 82 lines · 25 tokens per session scan A 963ce0f9b522
lint-runner is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 885 once invoked, about $0.0001 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-31.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
batch-bug-shepherd
Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…