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-adoptgit 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-adopt)<a href="https://agentmods.dev/skills/slopstopper/plumb-line/plumb-line-adopt"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-adopt/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-adopt"><img src="https://agentmods.dev/badge/skills/slopstopper/plumb-line/plumb-line-adopt.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.02092 |
| Opus 5 | $0.00000 | $0.01046 |
| Sonnet 5 | $0.00000 | $0.00418 |
| Haiku 4.5 | $0.00000 | $0.00209 |
Grade A, and why
plumb-line-adopt 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 11d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adopt plumb-line — which part, on what
REQUIRED READING FIRST: reference/fit-map.md (plugin root). If this file
cannot be read, stop immediately and report: "Cannot route: reference/fit-map.md
is missing or unreadable. Do not recommend from memory — the fit map is the
source of truth for what the primitives are for." Read
reference/portable-principles.md only if the conversation needs the
principles named; the fit map is sufficient for routing.
This skill is a concierge for the whole toolkit — the four sibling skills AND the run-time primitives. Its job is the question the docs cannot answer for a specific repo: "what would I use this on, here?" It recommends only. It never edits files, installs anything, or scaffolds code; every action belongs to the skill it hands off to.
1. Look — a lightweight, read-only scan
Scan the repository for routing signals only (this is not an audit — do not read whole files; filenames, imports, and greps suffice):
- HTTP ingestion:
requests/httpx/fetch/axioswhose results feed computation; caching or retry-with-cache logic. - Dataframes:
pandas/numpyimports;fixtures/,sample_data/, or demo CSVs loadable by production-adjacent code. - LLM or agent surface: LLM SDK calls; fallback/canned-response branches; agent-generated artifacts consumed downstream.
- Fakery near production paths: mock flags,
USE_MOCK-style toggles, stub data on non-test paths. - Existing adoption:
plumb-line-provenancealready imported; a ruleset file (AGENTS.md/CLAUDE.md) declaring layers; installed hooks.
State your denominator. Say in one line what the scan covered (e.g. "scanned imports and top-level layout; did not read function bodies") — a routing recommendation must not imply deeper knowledge than the scan had.
2. Ask — at most three questions
Fill only the gaps scanning cannot see. Good questions: what the builder is actually worried about; whether the mock/fixture data ever reaches users or stored outputs; whether they want enforcement or just visibility. Skip any question the scan already answered. If no builder is present to answer, route from the scan alone and say so.
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.
- 11d ago First seen · 175 lines · 0 tokens per session scan A 6d2e69cfece2
plumb-line-adopt is a skill published in the GitHub repository slopstopper/plumb-line (4 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,092 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-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-testing
Craftsman standard for automated testing: strategy, unit/integration/e2e selection, refactor-proof design, flaky tests, mocking boundaries, deterministic data, and merge-gate policy. Use WHENEVER work touches tests: writing/reviewing tests, strategy, "add tests", "why is this flaky", "what should I test", "tests pass…
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-frontend
The Craftsman standard for frontend application architecture — components, state management, data fetching, forms, routing, client/server boundaries, performance, error boundaries, and bundle size. Use this WHENEVER the work touches the application layer of a frontend: building components, wiring up API calls…