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 slopstopper/plumb-line --skill plumb-line-remediategit clone --depth 1 https://github.com/slopstopper/plumb-lineWrote 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/slopstopper/plumb-line/plumb-line-remediate)<a href="https://agentmods.dev/skills/slopstopper/plumb-line/plumb-line-remediate"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-remediate/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/slopstopper/plumb-line/plumb-line-remediate"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-remediate.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.00051 | $0.03638 |
| Opus 5.5 | $0.00020 | $0.01455 |
| Sonnet 5.5 | $0.00010 | $0.00728 |
| Haiku 4.5 | $0.00005 | $0.00364 |
Grade A, and why
plumb-line-remediate 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 26d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remediate plumb-line audit findings
REQUIRED READING FIRST: reference/portable-principles.md (plugin root).
If this file cannot be read, stop immediately and report: "Cannot remediate:
reference/portable-principles.md is missing or unreadable. Do not proceed from
memory — the principles file is the source of truth for what a fix must honor."
The audit finds; this skill fixes. The two never blur: remediation runs only on
an explicit invitation, consumes a report the audit produced (any
report-format: v1+; v4 is current), and applies nothing the builder has not
seen. If there is no report, offer to run plumb-line-audit first, or accept
findings pasted in the findings-table shape (Path / Line / Function / Status /
Issue / Suggested Fix / Principle; a v3 or earlier table has no Status).
Validate the report before consuming it. This skill acts on a contracted
input, so check the contract. The checker ships inside this plugin
(<plugin root>/scripts/check_report_format.py; scripts/check_report_format.py
inside the plumb-line repo):
python3 <plugin root>/scripts/check_report_format.py <the report>
A violation is not a reason to refuse the run — it is a reason to say what is wrong before acting on it. Report the violations, then ask whether to proceed; the risk a malformed report carries is that a column means something other than you assume, and the builder is the one who can tell. If the checker is unavailable, say the input was not mechanically validated rather than staying silent — the same honesty the audit owes its own output.
The contract (what a remediation run IS)
A remediation run produces, in order:
- a fix plan — every finding classified before any edit,
- per-finding diffs — each shown before it is considered done,
- a remediation record — the finding→change table that gives the remediation itself the lineage it demands of the code (P8 — State-first lineage),
- a verification step — the project's own enforcement, run, with output.
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.
- 26d ago Changed · +39 lines 7ee1c252908f
- 29d ago Changed · +14 lines 67e566455a7c
- 1mo ago Changed · +8 lines f7750a9c2976
- 1mo ago Changed f50595ce7fb9
- 1mo ago First seen · 216 lines · 51 tokens per session scan A 92227ae4d3eb
plumb-line-remediate is a skill published in the GitHub repository slopstopper/plumb-line (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 3,638 once invoked, about $0.0002 per session on Opus 5.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…
loud-errors
Use when you spot a swallowed, vague, or context-losing error — an empty catch, a bare except: pass, catch (e) { console.log(e) } that then continues, throw new Error("something went wrong"), an error logged then ignored, or a caught exception that drops its cause. Makes failures loud and specific: each error says…
delete-this
Use when a codebase feels heavy, when you suspect dead code, or before adding a feature to an area that's already cluttered. Finds and safely removes code that no longer earns its place — dead branches, unused exports, commented-out blocks, abandoned feature flags, speculative abstractions used once, and TODOs from a…
fix-it-now
Use the moment a real bug is found during any task — an audit, a review, a test wave, unrelated feature work — and the temptation appears to document it and move on. Defaults to fixing confirmed bugs in the current pass: a found bug is work surfaced, not work deferred. If a fix genuinely can't happen now (out of…
recipe-diagnose
Investigate problem, verify findings, and derive solutions.
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…