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 gul-labs/craftsman-marketplace/plugin install craftsmanWrote 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/gul-labs/craftsman-marketplace/craft-lint)<a href="https://agentmods.dev/skills/gul-labs/craftsman-marketplace/craft-lint"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-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/skills/gul-labs/craftsman-marketplace/craft-lint"><img src="https://agentmods.dev/badge/skills/gul-labs/craftsman-marketplace/craft-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.00147 | $0.01899 |
| Opus 5 | $0.00073 | $0.00949 |
| Sonnet 5 | $0.00029 | $0.00380 |
| Haiku 4.5 | $0.00015 | $0.00190 |
Grade A, and why
craft-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 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Craft
This skill owns linting as a first-class code-quality surface for JS/TS ESLint. Version choice matters, but the real standard is the resolved rule contract: typed linting, runtime-risk rules as errors, context-specific React/Next/a11y/security rules, and a zero-warning gate that developers and CI both run.
Applicability. If discovery finds no JS/TS ESLint surface — e.g. Python-only with Ruff,
Biome-only (no ESLint), Go with golangci-lint, Rust with clippy — mark the domain N-A or
partial with a one-line reason (what linter is present). Do not demand ESLint 10 flat config
on a non-ESLint stack. This skill does not expand into a multi-linter catalog; honest N-A is correct.
Operating principle — discover before you build
Do not judge a lint setup from config prose alone. First confirm ESLint is in scope (see
applicability). Then fetch the resolved ESLint rules for real source files with
eslint --print-config wherever possible, and compare those resolved rules against the standard for
that project's context.
If --print-config fails, record the failure and fall back to direct config-file inspection. A failed
resolved-config extraction is itself a finding: the team cannot reliably reason about what linting is
actually enforcing.
Workflow
-
Discover
- Read package manager files,
package.json, ESLint configs, TS configs, formatter configs, CI, husky/lint-staged, and workspace layout. - Identify project contexts: TypeScript library, Node/API/worker, Next app, React UI, JS-only app, docs/content-only package.
- Identify ESLint major/version and plugin versions.
- Read package manager files,
-
Extract resolved rules
-
Prefer the helper script in
scripts/eslint-rule-audit.mjs. -
Run it against the target repo. The plugin is installed outside the project, so always address the script through
${CLAUDE_PLUGIN_ROOT}rather than a relative or guessed path:node "${CLAUDE_PLUGIN_ROOT}/skills/craft-lint/scripts/eslint-rule-audit.mjs" /absolute/path/to/target-repo
-
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 · 121 lines · 147 tokens per session scan A 85d45d58d30a
craft-lint is a skill published in the GitHub repository gul-labs/craftsman-marketplace (1 stars, last pushed today), licensed MIT. It adds 147 tokens to every session and 1,899 once invoked, about $0.0007 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
plumb-line-audit
Use when auditing a diff or repository against the plumb-line principles — finds laundered uncertainty, boundary leaks, hardcoded priors, overstated maturity, outputs lacking recorded lineage, and baseline drift with no explanation. Read-only: it reports, never auto-fixes.
explain-back
Use before trusting, merging, or building on top of code you (or an agent) just wrote or are about to change. The agent explains the code back in plain language — what it does, why it exists, what breaks if it's wrong — and refuses to proceed until the mental model is confirmed. Use when a diff looks fine but nobody…
prove-every-number
Use whenever code contains a numeric constant, threshold, default, rate, capacity, tolerance, or coefficient — especially one the agent just introduced. Enforces the rule: every number is either derived (from real data or first principles, traceably) or cited (to a spec, datasheet, standard, or documented decision) …
boyscout
Use when touching an existing file to make a change, so you leave it slightly cleaner than you found it without derailing into a giant refactor. Identifies small, safe, in-scope improvements adjacent to the change you're already making — a better name, a deleted dead line, an extracted helper, a clarified condition …
why-comments
Use when a file is littered with comments that narrate what the code already says (// increment the counter), when load-bearing code has no explanation of why it exists, or when reviewing AI-generated code (agents pad output with narration and never record the why). Deletes comments that restate the code, keeps and…
everywhere-else
Use immediately after fixing a bug or improving a pattern in one place — before reporting done. Asks the question agents never ask themselves: 'did you do that anywhere else?' Enumerates the full population of sibling sites (other templates, scenarios, endpoints, components, fixtures, configs that share the same…