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 LerianStudio/ring --skill fixing-lintgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/fixing-lint)<a href="https://agentmods.dev/skills/lerianstudio/ring/fixing-lint"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/fixing-lint/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/lerianstudio/ring/fixing-lint"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/fixing-lint.svg" alt="Reviewed on agentmods" width="80" 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.00096 | $0.01241 |
| Opus 5.5 | $0.00038 | $0.00496 |
| Sonnet 5.5 | $0.00019 | $0.00248 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
ring:fixing-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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linting Codebase
When to use
- User runs /ring:fixing-lint command
- Codebase has lint issues that need fixing
- Multiple lint errors across different files/components
Skip when
- Single lint error → fix directly without agent dispatch
- Lint already passes → nothing to do
- User only wants to see lint output, not fix
Run lint checks, group issues into independent streams, dispatch parallel agents, iterate until clean.
⛔ Critical Constraints (communicate to ALL dispatched agents)
- DO NOT create automated scripts to fix lint issues
- DO NOT create documentation or README files
- DO NOT add comments explaining the fixes
- Fix each issue directly by editing source code
- Minimal changes — only what's needed for lint
Phase 1: Run Lint
Detect command: make lint → npm run lint → yarn lint → pnpm lint → golangci-lint run → cargo clippy → ruff check . → eslint .
<lint_command> 2>&1 | tee /tmp/lint-output.txt; echo "EXIT_CODE: ${PIPESTATUS[0]}"
If EXIT_CODE is non-zero, lint failed. Report failure clearly before proceeding to grouping.
Parse: file path, line:column, error code/rule, message, severity.
Phase 2: Group into Streams
| Issue Count | Grouping Strategy |
|---|---|
| < 10 | By file |
| 10-50 | By directory |
| 50-100 | By error type/rule |
| > 100 | By component/module |
A stream is independent if: files don't import each other, fixes won't conflict, agents can work without knowledge of other streams.
Phase 3: Parallel Agent Dispatch
⛔ STOP-CHECK BEFORE DISPATCH
Before emitting any Task call, count the agents you intend to launch in this turn.
- Count MUST equal the number of independent streams you identified in Phase 2.
- If your dispatch count diverges from your stream count → STOP and reconcile against the Phase 2 grouping.
- One agent per stream. No substitutions, no omissions.
⛔ MUST NOT trickle-dispatch
All stream agents leave in the SAME TURN, before reading any agent output.
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.
- 1mo ago First seen · 121 lines · 96 tokens per session scan A af1a379e4c46
ring:fixing-lint is a skill published in the GitHub repository LerianStudio/ring (218 stars, last pushed 4d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,241 once invoked, about $0.0004 per session on Opus 5.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
antidote
Stop AI agents from patching symptoms. Use this skill when coding, reviewing, refactoring, auditing, committing fixes, or adding guards, validation, workarounds, or 20+ lines without deleting code.
debug
Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.
prune
Use this agent to find and safely remove dead code and duplicate code — unused imports, unused exports, and copy-paste blocks — in any codebase.
refactor
Audit an existing project against its standards and apply selected improvements while preserving behavior.
scalpel
Surgical AI for your codebase. Plugs into any project, performs a 12-dimension diagnostic scan (git forensics, architecture, tech debt, security, infrastructure), delivers a Codebase Vitals health score, then assembles and manages an adaptive AI surgical team calibrated to YOUR project. Pendrive architecture — plug…
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.