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-bootstrapgit 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-bootstrap)<a href="https://agentmods.dev/skills/slopstopper/plumb-line/plumb-line-bootstrap"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-bootstrap/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-bootstrap"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-bootstrap.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.00073 | $0.03900 |
| Opus 5 | $0.00036 | $0.01950 |
| Sonnet 5 | $0.00015 | $0.00780 |
| Haiku 4.5 | $0.00007 | $0.00390 |
Grade A, and why
plumb-line-bootstrap 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap a project with plumb-line
Part of the five-skill flow: find your fit with plumb-line-adopt, learn the
discipline with plumb-line-method, set the project up here, review changes
with plumb-line-audit, and apply findings with plumb-line-remediate.
REQUIRED READING FIRST: reference/portable-principles.md and
adapters/adapter-contract.md (plugin root).
If either file cannot be read, stop immediately and report which file is missing. Do not proceed from memory.
Two entries: full bootstrap vs. declaration-only (mid-audit)
This skill has two entry modes. Full bootstrap — the builder asked for
setup — runs every step below. Declaration-only — plumb-line-audit
invoked this skill because the project declares no architecture and the audit
needs that context before proceeding — runs a deliberately two-minute detour:
- Ask ONLY interview questions 1–3 (layers + direction; source-truth layer; composition root). The audit needs the declaration, not the ceremony.
- Write the ruleset from those answers (Step 3), marking every section the
interview did not reach as
planned— an un-asked question must not read as an answered one. - Skip Step 4, Step 4b, and Step 6's audit offer entirely: no enforcement install, no primitive offer, nothing added to the project beyond the ruleset file. Those belong to a full bootstrap run — name it as the follow-up in the report's TODOs.
- Emit the Step 5 report header with one extra line —
entry: declaration-only— then return the baton: the calling audit resumes with the freshly declared architecture (do not start a second audit).
The honesty constraint applies in both modes: if the builder cannot name a source-truth layer, stop and say so — in declaration-only mode that answer goes back to the audit, which then proceeds calibrated with the gap on record.
Step 1 — Detect language, pick the adapter
- Look for
package.json-> JS adapter (adapters/js). - Look for
pyproject.toml/setup.py/requirements.txt-> Python adapter (adapters/python). - If both or neither, ASK the builder which to use. Never guess silently.
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 · 291 lines · 73 tokens per session scan A 1c61f46600e4
plumb-line-bootstrap is a skill published in the GitHub repository slopstopper/plumb-line (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 73 tokens to every session and 3,900 once invoked, about $0.0004 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…
craft-audit
The front door to the craft skills — a whole-project production-readiness orchestrator that drives the ten per-domain craft skills (ux, frontend, backend, db, security, infra, observability, testing, lint, ai) instead of auditing one surface at a time. It discovers the project's shape, plans an audit per surface, and…
craft-ai
The Craftsman standard for LLM-powered features — prompt-injection surface, key and spend protection, PII reaching model APIs, and reliability/eval discipline. Use whenever work touches an LLM integration: a chatbot or agent, a RAG pipeline, an LLM call from a route or job, tool/function-calling, or reviewing prompts…
craft-backend
The Craftsman standard for building and reviewing backend code — API routes, request validation, the authentication boundary, service/business logic, error handling, route rate-limit middleware, third-party integrations, and background jobs. Use this WHENEVER the work touches the server side: adding or reviewing a…
craft-infra
The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production…
craft-observability
The Craftsman standard for production observability — error tracking (Sentry), metrics & dashboards (Grafana), structured logging, tracing, SLOs, and alerting. Use this WHENEVER the work touches observability: adding or reviewing Sentry, wiring Grafana/Prometheus/OpenTelemetry, setting up structured logs, defining…