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.
git clone --depth 1 https://github.com/andrei-isvoran96/claude-skill-labWrote 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/commands/andrei-isvoran96/claude-skill-lab/lint)<a href="https://agentmods.dev/commands/andrei-isvoran96/claude-skill-lab/lint"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/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/commands/andrei-isvoran96/claude-skill-lab/lint"><img src="https://agentmods.dev/badge/commands/andrei-isvoran96/claude-skill-lab/lint.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.00000 | $0.00987 |
| Opus 5 | $0.00000 | $0.00494 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00099 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run all project linters in parallel and report per-lane pass/fail. Pre-commit sanity check.
Arguments
Optional. If $ARGUMENTS is --fix, run the auto-fixers for linters that support fix mode. Otherwise run in check-only mode.
Steps
-
Run all linters in parallel — issue all Bash calls in a single turn so they execute concurrently. Do NOT run them sequentially.
Check-only mode (default):
- <LINTER_NAME_1>:
<LINTER_CHECK_CMD_1> - <LINTER_NAME_2>:
<LINTER_CHECK_CMD_2> - <LINTER_NAME_3>:
<LINTER_CHECK_CMD_3>
Fix mode (when
$ARGUMENTSis--fix):- <LINTER_NAME_1>:
<LINTER_FIX_CMD_1> - <LINTER_NAME_2>:
<LINTER_FIX_CMD_2> - <LINTER_NAME_3>:
<LINTER_FIX_CMD_3>
- <LINTER_NAME_1>:
-
Capture exit codes per linter. Each Bash call's exit status is the truth —
0= pass, anything else = fail. Don't grep the output for "error" strings; trust the exit code. -
Format a compact per-lane report. One line per linter, plus a summary. Keep raw linter output OUT of the final reply unless the linter failed — then include only the relevant error excerpts (truncate to ~10 lines per failed lane).
All passing:
✓ <LINTER_NAME_1> passed ✓ <LINTER_NAME_2> passed ✓ <LINTER_NAME_3> passed ✓ all linters green (3/3)
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 · 88 lines · 0 tokens per session scan A 7e8b1f13c9ed
lint is a command published in the GitHub repository andrei-isvoran96/claude-skill-lab (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 987 tokens. 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.