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 agentproto/ts --skill pb-build-packgit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/pb-build-pack)<a href="https://agentmods.dev/skills/agentproto/ts/pb-build-pack"><img src="https://agentmods.dev/badge/skills/agentproto/ts/pb-build-pack/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/agentproto/ts/pb-build-pack"><img src="https://agentmods.dev/badge/skills/agentproto/ts/pb-build-pack.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.00060 | $0.00983 |
| Opus 5.5 | $0.00024 | $0.00393 |
| Sonnet 5.5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
pb-build-pack 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pb-build-pack — author and import an agent PACK
Goal
Package capabilities as an agent pack (one folder, one root marker), validate it, then import it through the right surface — registry, BYO repo, or MCP tools — and confirm with a re-sync.
Prerequisites (reference by name): ap-tasks if you track the work on the
board; the pack machinery itself lives in this repo, not the daemon.
Steps
1. Read the committed SOP first
Read projects/guilde/docs/PACK-SOP.md before anything else. It is the
authoritative authoring SOP — folder layout, marker semantics, what each
doctype handler consumes. This playbook sequences the work; the SOP defines
the artifacts.
2. Scaffold with the authoring CLI
pnpm --filter @guilde/api run pack init <kind> <slug>
kind is one of company | agency | knowledge — the ROOT MARKER file
decides the doctype: COMPANY.md, AGENCY.md, or KNOWLEDGE.md. Never use
bare pnpm pack — that is a reserved pnpm builtin, not this CLI.
3. Validate BEFORE importing
pack validate <dir>
Scaffolds pass validate out of the box; fill in your content and re-run
until it passes. Validation is the gate between authoring and import.
4. Import through the right surface
- House/external registry: add the source to
PACK_REGISTRY(apps/api/src/config/pack-registry.ts) keyed bykind— external repos of any kind register like the house companies. - BYO repo onto an EXISTING guild:
connect_pack_repo(vaults the PAT; repo becomes a resolvable source for that guild). - New guild from a repo:
apply_company_from_repo({repo, kind, ...}). - New guild from a registry source:
apply_company({sourceId, entryId}). - Existing guild, one operator or corpus:
install_operator/apply_corpus.
Underneath, every import path is ONE ingress primitive:
applyPackageToScope({ scopeId, userId, pkg, includeHandlers?, installMode? })
installMode: append (default, multi-instance) | skip-existing |
upsert-by-slug (re-sync). includeHandlers filters which doctype handlers
materialize. All three call-sites (guild-create, corpus-apply,
operator-install) route through it.
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 · 100 lines · 60 tokens per session scan A e0adbe03dbc3
pb-build-pack is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 983 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).