Borrowing it
Nothing to install: this file belongs to arnaudgelas/K-Ops. 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/arnaudgelas/K-Ops/main/.claude/skills/lint-heal/SKILL.mdgit clone --depth 1 https://github.com/arnaudgelas/K-OpsWrote 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/arnaudgelas/k-ops/lint-heal)<a href="https://agentmods.dev/skills/arnaudgelas/k-ops/lint-heal"><img src="https://agentmods.dev/badge/skills/arnaudgelas/k-ops/lint-heal/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/arnaudgelas/k-ops/lint-heal"><img src="https://agentmods.dev/badge/skills/arnaudgelas/k-ops/lint-heal.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.00026 | $0.00612 |
| Opus 5 | $0.00013 | $0.00306 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
lint-heal 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 10d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint + Heal
Goal
Continuously improve vault quality and ensure structural integrity.
Deterministic audits (run first)
Before hand-scanning, run the deterministic surfaces and act on what they report:
verify-spans— claims whosequote=anchor is absent from the source (failed = fix the anchor or remove the claim).review-queue— one prioritised worklist of everything needing human judgment.next-action— the single highest-leverage next repair plus a convergence verdict (blocking/cleanup/converged).community-audit— concept clusters, high-centrality bridge nodes, fragile single-connector clusters, and cross-cluster knowledge gaps.check-content-drift— claims and answers whose cited source content-hash has changed since capture (drifted = revalidate the dependent claim/answer or re-anchor it).
Look for
- Contradictions between concept pages and source summaries (check
data/contradictions.json). - Unsupported claims (Key Claims lacking direct inline citations
[[Sources/src-<id>|src-<id>]]). - Dead-end pages with no backlinks or missing reciprocal Related Concepts/semantic predicate links.
- Duplicate concepts with inconsistent naming or missing from
notes/Indexes/Topic_Atlas.md. - Missing required sections in concept pages or source summaries.
- Missing required metadata fields or bad values in frontmatter.
- Mismatched answer memo scope/quality (durable must be shared with non-empty updates; memo-only must be private with no updates).
- PDF sources with strong evidence strength missing
extraction_coverage. - Imported report metadata mismatches.
- Mismatched or missing reciprocal semantic edge predicates (
supersedes::↔superseded_by::, symmetriccontrasts_with::, reverse links forpart_of::).
Safe actions
- Fix broken wikilinks (e.g. resolve spaces to underscores, fix file paths).
- Add missing required sections as empty scaffolds.
- Add missing frontmatter fields with safe defaults (e.g.
claim_quality: provisional,type: concept,source_status: active, etc.). - Fix missing or mismatched reciprocal semantic edge predicates.
- Move uncertain or unverified claims into Open Questions.
- Update
notes/TODO.mdfor unresolved items or pages needing human revalidation. - Ensure orphan concept pages are handled or reported in
notes/TODO.md(indexing is handled programmatically).
What ships with it
1 file 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.
- 10d ago First seen · 46 lines · 26 tokens per session scan A 3789ea246a4f
lint-heal is a skill published in the GitHub repository arnaudgelas/K-Ops (1 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 612 once invoked, about $0.0001 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
code-understand
Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + rg cross-file references) otherwise. Use this any time you (the coding agent) need to orient in an unfamiliar or large…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
report-issue-framework
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
link-health
Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP.
kb-lint
Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.