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 escoffier-labs/skillet --skill line-checkgit clone --depth 1 https://github.com/escoffier-labs/skilletWrote 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/escoffier-labs/skillet/line-check)<a href="https://agentmods.dev/skills/escoffier-labs/skillet/line-check"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/line-check/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/escoffier-labs/skillet/line-check"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/line-check.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.00048 | $0.01150 |
| Opus 5 | $0.00024 | $0.00575 |
| Sonnet 5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
line-check 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 12d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
line-check
A chef's line check before service: walk every station, score it, and leave with an ordered list of what to fix first. The output is not a wall of findings, it is a backlog sorted by leverage (impact relative to effort) that someone could start executing immediately.
Read-only. Never modify the repo during an audit. If the user wants fixes applied afterward, that is a separate step on a branch.
Stations
Walk all seven. Score each 0-5 (5 = exemplary, 3 = functional with real gaps, 1 = broken or absent, 0 = actively harmful).
| # | Station | What to check |
|---|---|---|
| 1 | Docs and onboarding | README answers what/why/how-fast; quickstart commands actually exist and match the code; examples are current |
| 2 | Agent-readiness | AGENTS.md or CLAUDE.md present and accurate; memory/handoff wiring if the project uses it (.brigade/, .claude/memory-handoffs/); build/test commands documented for agents |
| 3 | Tests and CI | Critical paths covered, not just happy paths; CI exists and is green; lint/format gates wired |
| 4 | Hygiene | .gitignore excludes agent dirs (.claude/, .codex/) and build artifacts; LICENSE present (critical if public); no secrets or credentials in the tree; stale branches |
| 5 | Structure | Oversized files and god modules; dead code; tangled responsibilities; dependency health (outdated, vulnerable, unused) |
| 6 | Release hygiene | CHANGELOG maintained; version in code matches latest tag; tags not far behind the default branch |
| 7 | TODO and issue mining | In-code TODO/FIXME/HACK markers and open issues, folded into the backlog rather than reported raw |
Station guidance:
- For station 2, if the brigade CLI is installed and the repo has brigade wiring, run
brigade handoff doctorandbrigade memory care scanand fold their output into findings. - For station 5, do not chase abstract purity. Find the friction that makes the code hard to change, and ask: what gets easier if this module disappears? Can a newcomer predict where the next change belongs?
- Respect .gitignore; never audit
node_modules/,vendor/,dist/, or other generated trees.
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.
- 12d ago First seen · 85 lines · 48 tokens per session scan A 3cdcb3b2fbb2
line-check is a skill published in the GitHub repository escoffier-labs/skillet (4 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 1,150 once invoked, about $0.0002 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
craft-fix
The Craftsman standard for driving fixes against an existing craft-audit workspace — "fix the findings", "fix SEC-003", "work through the audit", "start the climb". An ACTION skill, not a domain: it picks findings off the master tracker's climb sequence, re-verifies each is still real, gets the user's approval, and…
production-audit
Exhaustive production-readiness audit of any codebase or product. Runs diverse-angle discovery passes until two consecutive passes find nothing new, adversarially verifies every finding against the real code, and reports one flat severity-tagged list with file:line evidence. No summary, no hedging.
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
Reverse Engineering & Binary Analysis
Binary analysis, assembly interpretation, disassembly, decompilation, firmware RE, and protocol reverse engineering.
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.