Borrowing it
Nothing to install: this file belongs to luthersystems/elps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luthersystems/elps/main/.claude/skills/add-linter-check/SKILL.mdgit clone --depth 1 https://github.com/luthersystems/elpsWrote 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/luthersystems/elps/add-linter-check)<a href="https://agentmods.dev/skills/luthersystems/elps/add-linter-check"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/add-linter-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/luthersystems/elps/add-linter-check"><img src="https://agentmods.dev/badge/skills/luthersystems/elps/add-linter-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.00000 | $0.01667 |
| Opus 5.5 | $0.00000 | $0.00667 |
| Sonnet 5.5 | $0.00000 | $0.00333 |
| Haiku 4.5 | $0.00000 | $0.00167 |
Grade A, and why
add-linter-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 2d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/add-linter-check — New Lint Analyzer Skill
Adds a new static analysis check to the ELPS linter (lint/, run by elps lint, the LSP, and CI). This is a prescriptive workflow touching three Go files plus docs/lint-checks.md.
For Go-side invariants over elps's own source, use /elpsvet instead.
Trigger
Use when asked to add a new lint check or analyzer for ELPS source, when a new builtin/op/macro has structural requirements (see /implement), or when a behavior change needs a static migration diagnostic.
Workflow
1. Design the Check
Before writing code, answer:
- What pattern does this check detect? (name it with kebab-case, e.g.,
unused-import) - Is it a simple per-expression check (use
WalkSExprs) or context-sensitive (use custom walker)? - What's the diagnostic message? Keep it concise and actionable.
- What are the false positive risks? Plan mitigations.
2. File 1: lint/analyzers.go — Define the Analyzer
Add a new exported variable following this pattern:
var AnalyzerMyCheck = &Analyzer{
Name: "my-check",
Doc: "Check that ... (one-line description used by --list)",
Run: func(pass *Pass) error {
WalkSExprs(pass.Exprs, func(sexpr *lisp.LVal, depth int) {
head := HeadSymbol(sexpr)
if head != "target-form" {
return
}
// Check logic here
argc := ArgCount(sexpr)
if argc < 2 {
src := SourceOf(sexpr)
pass.Report(Diagnostic{
Message: "descriptive error message",
Pos: posFromSource(src.Source),
})
}
})
return nil
},
}
Available helpers:
WalkSExprs(exprs, fn)— Walk all s-expressions, calls fn with each sexpr and depthWalk(exprs, fn)— Walk ALL nodes (not just s-expressions)HeadSymbol(sexpr)— Get the operator name (e.g.,"if","defun")ArgCount(sexpr)— Count arguments (excludes the operator)SourceOf(v)— Get source location, falling back to first child if neededposFromSource(loc)— Convert*token.LocationtoPositionpass.Report(diag)— Report a diagnosticpass.Reportf(source, format, args...)— Printf-style diagnostic
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.
- 2d ago First seen · 167 lines · 0 tokens per session scan A 3fc073551a7e
add-linter-check is a skill published in the GitHub repository luthersystems/elps (36 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 1,667 tokens. 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-10-26.
Other skills, from other repositories
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…
kessoku-di
Kessoku compile-time DI with parallel initialization for Go. Use when writing or debugging kessoku providers/injectors, enabling async dependencies, migrating from google/wire, or fixing go:generate/codegen issues in Go services.
functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…
go-performance
Use when a workload or budget can change the mechanism, or when an optimization claim needs a comparable baseline, attribution, and delta.
golang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log…