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 phuonghx/aim-cli --skill lint-and-validategit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/lint-and-validate)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/lint-and-validate"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/lint-and-validate/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/phuonghx/aim-cli/lint-and-validate"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/lint-and-validate.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.00084 | $0.00524 |
| Opus 5.5 | $0.00034 | $0.00210 |
| Sonnet 5.5 | $0.00017 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
lint-and-validate 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.
What it actually says
Lint and Validate
Treat validation as part of writing the code, not a separate chore. Code is not "done" while a checker still complains.
Toolchain by ecosystem
Node.js / TypeScript
- Style + autofix --
npm run lint, ornpx eslint "<path>" --fixwhen there is no script - Type safety --
npx tsc --noEmit - Dependency audit --
npm audit --audit-level=high
Python
- Lint + autofix --
ruff check "<path>" --fix(fast, covers most rules) - Static security --
bandit -r "<path>" -ll - Type safety --
mypy "<path>"
The validation loop
- Make the edit.
- Run the relevant checks, e.g.
npm run lint && npx tsc --noEmit. - Read the output carefully -- look at the final summary, not just the exit code.
- Fix what it reports and re-run. Repeat until clean. Reporting code as finished while the summary shows failures is not acceptable.
When a step fails
- Linter complains -- resolve the style or syntax problem right away; many issues autofix.
- Type check complains -- reconcile the type mismatch before moving on.
- No tooling configured -- look for
.eslintrc,tsconfig.json, orpyproject.tomlin the project root and propose adding the missing config rather than skipping the check.
Non-negotiable: nothing gets committed or called complete until these checks pass.
Scripts
| Script | What it does | How to run |
|---|---|---|
scripts/lint_runner.py |
Detects the stack and runs its linters/type checks | python scripts/lint_runner.py <project_path> |
scripts/type_coverage.py |
Estimates type-annotation coverage | python scripts/type_coverage.py <project_path> |
What ships with it
2 files 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.
- 1mo ago First seen · 46 lines · 84 tokens per session scan A 264f5de48df6
lint-and-validate is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 524 once invoked, about $0.0003 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-31.
Other skills, from other repositories
evidence-audit
Evidence-led audit/fix rounds for any codebase in any language. Finds only defects that a runnable proof reproduces on current code, applies the narrowest in-scope patch, verifies with a second proof, promotes high-risk proofs to permanent regression tests, and reports exact validation results. Use whenever the user…
bug-hunter
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and verify one real defect. Trigger on the explicit vocabulary — "bug", "bug hunt", "/bughunt", "scan for issues", "find problems"…
debugging
Use this skill when something is broken and the cause is unknown — a failing test, a crash, an error message, wrong output, a regression, a hang, or behaviour that differs between environments — and it has to be found and fixed at the root. Also use it to build the failing proof for a suspected defect before fixing…
observability
Use this skill when adding or reviewing logging, metrics, or tracing in an application, or when a production problem can't be diagnosed from the signals that exist today. Triggers: user says "logging", "logs", "trace", "tracing", "metrics", "observability", "instrument", "OpenTelemetry", "structured logging", "log…
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
incident-response
Diagnose and recover an owned service incident with bounded changes, timeline evidence and verified health. Use during outages, bad deployments or data/service degradation; preserve evidence and separate mitigation from root-cause repair.