Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add int2t05/engineering-skills/plugin install engineering-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/int2t05/engineering-skills/linting)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/linting"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/linting.svg" alt="Measured on agentmods" 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.00128 | $0.01344 |
| Opus 5 | $0.00064 | $0.00672 |
| Sonnet 5 | $0.00026 | $0.00269 |
| Haiku 4.5 | $0.00013 | $0.00134 |
Grade A, and why
linting 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linting
Fix machine-detectable code issues — run the project's linters and static analyzers, resolve or justifiably suppress findings, and tighten config so real issues surface and noise dies down. This is the automated quality gate, not a substitute for human review.
When to use
- Fixing a failing lint/static-analysis gate in CI or a pre-commit hook
- Tightening lint rules — turning on stricter rules, removing broad ignores, paying down
eslint-disabledebt - Running static analysis (type checkers, security linters, complexity analyzers) and triaging findings
- Establishing lint config for a new project or after a toolchain migration
- Triggers on "lint", "linting", "fix eslint", "static analysis", "lint 修复", "静态分析", "格式检查", "代码规范检查"
Not for: human-judgment review of a diff — smells, spec faithfulness, design (use code-review); diagnosing runtime behavior bugs (use debugging); behavior-preserving structural moves like extracting or splitting modules (use refactoring).
Steps
1. Detect the toolchain
Read the project before running anything. Don't impose a linter the project doesn't use.
- Find lint config and scripts:
package.json(lintscript,eslint/biome/prettierconfig),pyproject.toml/setup.cfg(ruff/flake8/mypy),Cargo.toml(clippy),.golangci.yml,.editorconfig. - Find the CI gate — what command does CI actually run? Lint locally with the same command, or you'll fix issues CI doesn't see and miss issues CI blocks on.
- If no toolchain exists, ask before introducing one — adding a linter is a project decision, not a drive-by.
2. Run and capture all findings
Run the linter/analyzer and capture the full output. Don't fix as you go — get the complete picture first so you can triage by category, not react to the first error.
- Run with the project's configured command. For a first pass, also run with
--max-warnings 0(or equivalent) so warnings don't slip past. - Capture the raw output; note the rule code for every finding (e.g.
@typescript-eslint/no-explicit-any,F401,E501). The rule code is how you triage and how you suppress.
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 · 80 lines · 128 tokens per session scan A 65d14f91106a
linting is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 7d ago), licensed MIT. It adds 128 tokens to every session and 1,344 once invoked, about $0.0006 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
pr-workflow
Crear pull requests completas con descripcion, labels y reviewers.
sonarqube
Levantar SonarQube con Docker, analizar el código y proponer mejoras. También: análisis estático, deuda técnica, code smells, cobertura, calidad automatizada.
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
second-pass-review
Independent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.