Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/lonormaly/builders-stacknpx agentmods add skills/lonormaly/builders-stack/add-a-libWrote 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/lonormaly/builders-stack/add-a-lib)<a href="https://agentmods.dev/skills/lonormaly/builders-stack/add-a-lib"><img src="https://agentmods.dev/badge/skills/lonormaly/builders-stack/add-a-lib/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/lonormaly/builders-stack/add-a-lib"><img src="https://agentmods.dev/badge/skills/lonormaly/builders-stack/add-a-lib.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.00717 |
| Opus 5.5 | $0.00032 | $0.00287 |
| Sonnet 5.5 | $0.00016 | $0.00143 |
| Haiku 4.5 | $0.00008 | $0.00072 |
Grade A, and why
add-a-lib 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a lib
A libs/* package is shared code that is never served — other packages consume it, it consumes nobody upward. Reach for this when the same helper/type/component is about to exist in two places.
When to use
- A util, type, component, or client is needed by 2+ apps/services → extract it into a lib.
- Not when it's used in exactly one place — leave it there (YAGNI). A lib for one consumer is premature.
Steps
-
Pick the name.
libs/<name>, package@stack/<name>. Keep it a role, not a feature (ui,db,auth,ai,analytics). -
Create the folder + files:
libs/<name>/ ├── package.json ├── tsconfig.json └── src/ └── index.ts # the ONE public door -
package.json— name it@stack/<name>, point exports at the barrel:{ "name": "@stack/<name>", "private": true, "type": "module", "exports": { ".": "./src/index.ts" }, "scripts": { "typecheck": "bash ../../scripts/typecheck-native.sh --noEmit" } } -
tsconfig.json— extend the root base, never fork options:{ "extends": "../../tsconfig.base.json", "include": ["src"] } -
src/index.ts— this is the only thing consumers may import. Re-export the public surface; keep everything else internal:export { thing } from "./thing"; export type { ThingOptions } from "./thing"; -
Install so the workspace links it:
bun install(root). The@stack/<name>name now resolves across the workspace.bun run check:typescriptenforces the shared stable TypeScript 7 checker for every workspace. -
Consume it from an app/service by package name only:
import { thing } from "@stack/<name>"; // ✅ import { thing } from "@stack/<name>/src/internal/thing"; // ❌ deep import — forbidden
Rules to respect
- No upward import: the lib must not import from
apps/orservices/. If it needs to, the boundary is wrong — the caller should pass the dependency in. - One public door: anything not exported from
src/index.tsis private. Don't let consumers reach into internals. - No Tiltfile change — libs aren't served, so they get no Tilt resource.
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.
- 1mo ago First seen · 73 lines · 81 tokens per session scan A 154f9cd760d7
add-a-lib is a skill published in the GitHub repository lonormaly/builders-stack (42 stars, last pushed 20d ago), licensed MIT. It adds 81 tokens to every session and 717 once invoked, about $0.0003 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-30.
Other skills, from other repositories
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.
hono-core
Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.
sora-client
A typed TypeScript client for calling Sora tools as functions from code. It can call tools for tasks such as search, fetching page text, addresses, and weather, then filter the results before returning selected fields.
sora-client
A typed TypeScript client for calling Sora tools as functions from code. It can call tools for tasks such as search, fetching page text, addresses, and weather, then filter the results before returning selected fields.
widen-return-type
When delegating a task affected by this skill, include.
drizzle-orm
Use when modeling data or querying with Drizzle ORM in TypeScript — pgTable schema in .ts, type-safe select/insert/relational queries, drizzle-kit migrations. NOT Prisma Client or schema.prisma (that is prisma-orm), NOT ORM-agnostic migration strategy (that is db-migrations), NOT Postgres engine tuning or EXPLAIN…