Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/softspark/ai-toolkitnpx agentmods add skills/softspark/ai-toolkit/lintWrote 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/softspark/ai-toolkit/lint)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/lint"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/lint.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 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 39 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 63 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 69 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 118 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 39 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 66 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.00047 | $0.01164 |
| Opus 5 | $0.00023 | $0.00582 |
| Sonnet 5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00116 |
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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Runner
$ARGUMENTS
Run linting and type checking based on detected project type.
Project context
- Project files: !
ls pyproject.toml package.json composer.json pubspec.yaml go.mod 2>/dev/null
Auto-Detection
Run the bundled script to detect available linters:
python3 ${CLAUDE_SKILL_DIR}/scripts/detect-linters.py .
Usage
/lint [path]
Commands by Project Type
| Project Type | Lint Command | Type Check |
|---|---|---|
| Python | ruff check . |
mypy . |
| TypeScript/Node | npx eslint . |
npx tsc --noEmit |
| PHP | ./vendor/bin/phpstan analyse |
- |
| Go | golangci-lint run |
- |
| Rust | cargo clippy |
- |
| Flutter/Dart | dart analyze |
- |
Python Projects
# Linting
ruff check .
# Type checking
mypy .
# Auto-fix
ruff check --fix .
ruff format .
TypeScript/Node Projects
# Linting
npx eslint .
# Type checking
npx tsc --noEmit
# Auto-fix
npx eslint --fix .
PHP Projects
# Static analysis
./vendor/bin/phpstan analyse
# Code style
./vendor/bin/phpcs
./vendor/bin/phpcbf # auto-fix
Docker Execution (if applicable)
# Generic pattern - replace {container} with your app container
docker exec {container} make lint
docker exec {container} make typecheck
Quality Gates
- Linting: 0 errors
- Type checking: 0 errors (for new code)
Common Issues
| Error | Fix |
|---|---|
| Missing type hints | Add type annotations |
| Unused imports | Remove or use # noqa: F401 |
| Line too long | Break line or disable for that line |
| Import order | Let linter fix with --fix |
Rules
- MUST auto-detect the linter from project config (
pyproject.toml,package.json,.eslintrc.*,composer.json,go.mod,Cargo.toml,pubspec.yaml) — do not assume - MUST show the diff before applying any
--fixrun; the user owns the decision to accept auto-fixes - NEVER suppress lint errors with blanket
# noqaoreslint-disable-next-linewithout naming the specific rule and a reason - NEVER run the formatter (ruff format, prettier, dprint) inside a lint pass unless the project has that wired explicitly — formatting and linting are separate concerns
- CRITICAL: report the error count before and after any auto-fix — delta visibility is what makes the run trustworthy
- MANDATORY: respect the project's lint config (
.ruff.toml,eslint.config.js,phpstan.neon) — overriding project rules on the fly produces arguments during code review
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.
- 4d ago First seen · 130 lines · 47 tokens per session scan A 1f713a3b5eaf
lint is a skill published in the GitHub repository softspark/ai-toolkit (170 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 1,164 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
cline-fix-volatile-msg
Ladder-aware Cline Anthropic caching — verify the rolling read/write ladder on the wire, then add the tools breakpoint and tune TTL. Updated for the 2026-08 AI-SDK monorepo.
continue-fix-volatile-msg
Ladder-aware Continue Anthropic caching — verify the rolling ladder on the wire, then enable it by default and add TTL coverage.
opencode-detect-openai-compat
OpenCode's caching detection misses OpenAI-compatible proxies routing to Anthropic/Bedrock. Broaden the predicate.
cline-pin-timestamp
Cline's system prompt includes a timestamp that may be recomputed per request, invalidating the system-prompt cache.
log-analyzer
Senior-SRE log analysis specialist. Use when investigating incidents from logs, triaging error spikes, extracting timelines, correlating distributed traces, or separating signal from noise across plain-text, JSON (slog/zap), syslog, journald, container, and Kubernetes logs. ALWAYS use when the user asks to "analyze…
incident-postmortem
Incident post-mortem specialist for writing blameless post-mortems, extracting timelines from logs/events, conducting root cause analysis (5-Why, fishbone), classifying severity, and generating tracked action items. ALWAYS use when writing a post-mortem, reviewing an incident, extracting a timeline, performing root…