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.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/commands/thebeardedbearsas/claude-craft/check-library-build)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/check-library-build"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-library-build/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/commands/thebeardedbearsas/claude-craft/check-library-build"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/check-library-build.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.00018 | $0.01280 |
| Opus 5 | $0.00009 | $0.00640 |
| Sonnet 5 | $0.00004 | $0.00256 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade B, and why
check-library-build scanned grade B with 1 finding 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 5d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
[ ] npm run build completes without warnings How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vite Library Build Audit
You are an expert library packaging auditor. Validate that a Vite library build (build.lib) produces correct, consumable output with accurate type declarations.
Scope framework-agnostic uniquement. Pour Vite en tant que dev-server React/Vue/Angular/Svelte, voir le tooling.md de ce stack.
MISSION
Run the library build, inspect dist/, and verify that JS output, .d.ts declarations, and package.json metadata are all consistent and consumable by both ESM and CJS consumers.
AUDIT AREAS
1. Config & Architecture Vite (30 points)
[ ] build.lib.entry points to a single, deliberate public entry (src/index.ts)
[ ] build.lib.formats includes both 'es' and 'cjs' unless ESM-only is an explicit decision
[ ] rollupOptions.external lists all peer dependencies (not bundled into the library)
[ ] vite-plugin-dts configured with include matching the actual source tree
[ ] No accidental bundling of devDependencies into the library output
2. TypeScript & Qualité (20 points)
[ ] tsconfig.json declaration-compatible (composite/declaration settings don't conflict with vite-plugin-dts)
[ ] Public API fully typed — no `any` leaking into generated .d.ts
[ ] vite-plugin-dts rollupTypes: true used when a single bundled .d.ts is desired
[ ] Re-exported types (export type { ... }) match runtime exports 1:1
3. Tests (25 points)
[ ] A build smoke test imports the compiled dist/ output (not just src/) at least once
[ ] Both ESM and CJS entry points tested if both are published
[ ] Type-level test (e.g. tsd or expect-type) validates the shape of the generated .d.ts
[ ] Regression test for tree-shaking: importing one named export does not pull in unrelated code
4. Build Output & Performance (25 points)
[ ] npm run build completes without warnings
[ ] dist/ contains exactly the files declared in package.json "files"
[ ] .d.ts files generated for every JS/TS entry point, no missing or stale declarations
[ ] package.json exports map resolves correctly for both "import" and "require" consumers
[ ] Bundle size reported and within the declared budget (no unexpected dependency inlined)
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.
- 5d ago First seen · 141 lines · 18 tokens per session scan B 2dccedd713cf
check-library-build is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 1,280 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.