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 chadcorp/warden --skill build-productgit clone --depth 1 https://github.com/chadcorp/wardenWrote 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/chadcorp/warden/build-product)<a href="https://agentmods.dev/skills/chadcorp/warden/build-product"><img src="https://agentmods.dev/badge/skills/chadcorp/warden/build-product.svg" alt="Measured on agentmods" 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.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
build-product 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 7d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Product
Turn a validated idea into a complete, verified, shippable digital product — to a top-tier bar, with every artifact checked rather than assumed.
When to use
After an idea passes research-brain/idea-scout, or whenever asked to "build the
tracker / workbook / kit / app for X."
The protocol
-
Restate the buyer and the one job. A product that does one job superbly beats a bundle that does five jobs adequately. Write the single sentence of value the buyer gets.
-
Pick the smallest complete shape. Choose the format that fully delivers the job: a workbook, a single-file app, a playbook, a template set. Complete beats elaborate.
-
Design the spine first. Define the inputs, the core computation or logic, and the one or two views that prove it works. Everything else is overdelivery on top of a spine that must be correct.
-
Build with guards. For anything that computes:
- Handle the empty state (no data yet) without breaking.
- Make every total reconcile — to the cent — by an independent path.
- Never let a display value and a computed value disagree.
-
Verify each artifact, do not assume it. Open what you built. Recompute the numbers a second way. Confirm the files exist and contain what you expect. "It should work" is not "it works."
-
Overdeliver deliberately. Add the one or two extras that turn a fine product into one worth recommending — a starter template, a quick-start, a clear example walked end to end.
-
Prepare the hand-off. Assemble the listing kit (clear title, honest summary, the visual sequence) so the product can actually be found and bought.
Output
The finished deliverable plus a short build report: what it is, what was
verified and how, and any known limitation stated honestly. Hand the result to
build-brain/ship-gate for an independent GO/NO-GO — never gate your own work.
Honesty rule
If a number did not reconcile or a file did not open, fix it before you call it done. Report what you actually verified, not what you intended.
What ships with it
3 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.
- 7d ago First seen · 48 lines · 0 tokens per session scan A fe8c669850cf
build-product is a skill published in the GitHub repository chadcorp/warden (0 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 494 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
gmail-sync
API integration skill that fetches Gmail messages, syncs inbox labels, and processes attachments via the Gmail REST API. Use when fetching new emails, syncing inbox state, triaging unread messages, exporting mail data, or integrating Gmail into automated workflows.
orbit-general
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the…
orbit-gmail
Open Orbit briefing skill — selected by the Orbit pipeline when Gmail is the user's only connected connector, or when the user explicitly scopes their daily digest to Gmail. Pulls the past 24 hours of inbox activity (replies awaited, mentions, cc, auto- categorized bulk) from the user's authenticated Gmail connection…
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
discovery-question-form
Structured clarification form for unresolved material requirements.
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.