Borrowing it
Nothing to install: this file belongs to savant0x/savant-code. 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/savant0x/savant-code/main/.agents/skills/library-complete-needs-a-named-consumer/SKILL.mdgit clone --depth 1 https://github.com/savant0x/savant-codeWrote 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/savant0x/savant-code/library-complete-needs-a-named-consumer)<a href="https://agentmods.dev/skills/savant0x/savant-code/library-complete-needs-a-named-consumer"><img src="https://agentmods.dev/badge/skills/savant0x/savant-code/library-complete-needs-a-named-consumer/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/savant0x/savant-code/library-complete-needs-a-named-consumer"><img src="https://agentmods.dev/badge/skills/savant0x/savant-code/library-complete-needs-a-named-consumer.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.00017 | $0.00514 |
| Opus 5.5 | $0.00007 | $0.00206 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
library-complete-needs-a-named-consumer 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 13d 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.
What it actually says
Library-Complete Work Needs a Named Consumer
When to Use
Before closing any FID, plan or task that leaves an artifact with no production caller: a module with only its own suite, a limiter with no reader, a command with no entry point. "Ready for the first consumer" is a hand-off, and a hand-off is complete only when a live surface names the owner of the next step.
Procedure
- Name the live surface that will call the artifact, and say in the closure text which register item or active FID owns the wiring — a closed record is no longer a register item, so a limitation stated inside it is invisible to every register-shaped check.
- Create the wiring item in the same pass: a scope line with its write targets, or an active FID with its own gates.
- Prove the caller with Law 4 grep evidence before the feature is called complete.
Pitfalls
- Closing on "no production call path yet" as a stated limitation. The limitation leaves the record with the record, and no gate reads a closed record's prose.
- Delegating adoption to "its own registered item" without creating it: the delegation is a claim, the register line is the evidence.
- Offering a green module suite as the completeness argument. The suite proves the module; only the caller proves the feature.
Verification
- The wiring record exists (register item or active FID) and closes on Law 4 grep evidence naming the production caller.
bun run validate:repositorypasses: the disposition must be a register item or an active FID.
Re-authored from lesson: A library-complete hand-off needs a named consumer, not a readiness note (dev/LEARNINGS.md → Owning FID FID-2026-1006-003). The previous draft's description and "When to Use" were the read_files error string sliced at 60 characters and its Procedure was its own name — the defect FID-2026-1016-015 repaired in the drafter.
What ships with it
2 files 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.
- 13d ago Changed · +25 lines · -5 tokens per session 6652a606f502
- 14d ago First seen · 27 lines · 22 tokens per session scan A c06308a16c86
library-complete-needs-a-named-consumer is a skill published in the GitHub repository savant0x/savant-code (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 514 once invoked, about $0.0001 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-10-16.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.