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 baseballyama/eslint-plugin-postgresql --skill run-check-and-testgit clone --depth 1 https://github.com/baseballyama/eslint-plugin-postgresqlWrote 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/baseballyama/eslint-plugin-postgresql/run-check-and-test)<a href="https://agentmods.dev/skills/baseballyama/eslint-plugin-postgresql/run-check-and-test"><img src="https://agentmods.dev/badge/skills/baseballyama/eslint-plugin-postgresql/run-check-and-test.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.00061 | $0.01391 |
| Opus 5 | $0.00030 | $0.00696 |
| Sonnet 5 | $0.00012 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
run-check-and-test 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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality gate
This skill runs the project's full check set and reports back. It is language-
and tooling-agnostic: read the project's manifest (package.json,
Cargo.toml, pyproject.toml, Makefile, etc.) to discover the actual scripts.
Do not assume.
Discover the available scripts
Look in this order, depending on what's in the repo root:
| File | Where to look |
|---|---|
package.json |
scripts field (npm/pnpm/yarn/bun) |
Cargo.toml |
cargo fmt, cargo clippy, cargo test |
pyproject.toml |
[tool.*] sections, common: ruff, pytest, mypy |
Makefile |
Common targets: make check, make test, make lint |
justfile / Taskfile |
The recipes within |
mise.toml / .mise.toml |
Tasks defined under [tasks] |
CLAUDE.md |
Project-specific overrides may be documented here |
If the user has explicitly told you the commands once before in the session, use those. Otherwise re-discover — scripts get renamed.
The gates, in order
Run in this order; stop and report on the first failure unless the user said "run everything":
-
Format — does the code conform to the formatter?
- Common:
prettier --check/cargo fmt --check/ruff format --check/gofmt -l - If broken: try the auto-fix (
prettier --write/cargo fmt/ruff format) before reporting. Re-run the check after fixing.
- Common:
-
Lint — static analysis.
- Common:
eslint,oxlint,clippy,ruff check,golangci-lint - Some lint errors auto-fix; try
--fixor equivalent before reporting only the unfixable ones.
- Common:
-
Type check — for typed languages.
- Common:
tsc --noEmit,cargo check,mypy,pyright,go vet - Type errors are not auto-fixable; report them with file:line.
- Common:
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.
- 6d ago First seen · 126 lines · 61 tokens per session scan A a15df31807ee
run-check-and-test is a skill published in the GitHub repository baseballyama/eslint-plugin-postgresql (11 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 1,391 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.