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 rstackjs/agent-skills --skill migrate-to-rslintgit clone --depth 1 https://github.com/rstackjs/agent-skillsWrote 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/rstackjs/agent-skills/migrate-to-rslint)<a href="https://agentmods.dev/skills/rstackjs/agent-skills/migrate-to-rslint"><img src="https://agentmods.dev/badge/skills/rstackjs/agent-skills/migrate-to-rslint.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00463 |
| Opus 5 | $0.00028 | $0.00231 |
| Sonnet 5 | $0.00011 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
migrate-to-rslint 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.
What it actually says
Migrate to Rslint
Goal
Migrate lint tooling to Rslint with minimal behavior changes and clear validation.
Supported source linters
- ESLint flat config
Migration principles (must follow)
- Official docs first: treat Rslint docs as source of truth for CLI, config, inline directives, VS Code settings, rules, and presets.
- Smallest-change-first: migrate package, command, config, and editor wiring before changing source files.
- Preserve lint intent: keep supported rule severities/options where Rslint supports them; call out unsupported rules/plugins instead of silently dropping behavior.
- Do not rewrite inline directives by default: Rslint supports
eslint-disableandrslint-disable; replace prefixes only when the user asks. - Validate before cleanup: keep old linter dependencies/config until the Rslint command passes for the migrated scope, then remove obsolete linter-only artifacts.
Workflow
-
Detect source linter
- ESLint flat config:
eslint.config.*,eslintdependency, or package scripts that runeslint. - If the source linter is not covered by a reference yet, inventory the current behavior and explain that no dedicated migration reference exists.
- ESLint flat config:
-
Apply source-specific migration guide
- ESLint flat config:
references/eslint-flat-config.md
- ESLint flat config:
-
Validate behavior
- Run the migrated lint command.
- If the project had a fix command, run the migrated fix command only when appropriate for the task.
- Resolve config, rule, and editor-setting issues before removing legacy files.
-
Cleanup and summarize
- Remove obsolete linter dependencies/config after Rslint is green.
- Summarize changed files, migrated presets/plugins, unsupported gaps, and remaining manual follow-ups.
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.
- 8d ago First seen · 43 lines · 57 tokens per session scan A ab4861ac2085
migrate-to-rslint is a skill published in the GitHub repository rstackjs/agent-skills (93 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 463 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.