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 BlackBeltTechnology/pi-agent-dashboard --skill craft-brand-kitgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/craft-brand-kit)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/craft-brand-kit"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/craft-brand-kit/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/blackbelttechnology/pi-agent-dashboard/craft-brand-kit"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/craft-brand-kit.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.00088 | $0.03194 |
| Opus 5.5 | $0.00035 | $0.01278 |
| Sonnet 5.5 | $0.00018 | $0.00639 |
| Haiku 4.5 | $0.00009 | $0.00319 |
Grade A, and why
craft-brand-kit 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 3d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft-brand-kit — logo → vector variants → raster set → brand sheet → PDF package
Starts from a user-supplied logo (an svg is used as-is; a raster logo is traced with VectorCraft imageTrace).
VectorCraft makes the vector variants, PhotoCraft the raster export set, DesignCraft the one-page sheet, PdfCraft the package.
Read vectorcraft, photocraft, designcraft and pdfcraft first. Resumable-job rules are in the craft-studio router,
section Craft jobs. Passwords and API keys are never written to job.json, gate reports or step files.
Step table
| # | Step | Tool | Input → Output | Gate |
|---|---|---|---|---|
| 0 | Preflight + job | agent | request → job.json |
check: job |
| 1 | Logo to vector | VectorCraft | logo.svg or logo.png → 01-logo/logo.svg |
preview png + pi-craft verify --size --alpha |
| 2 | Variants | VectorCraft | logo.svg → 02-variants/logo-black.svg, logo-white.svg |
preview png + pi-craft verify --size |
| 3 | Raster set | PhotoCraft | logo.svg → 03-raster/logo-<w>.png, logo-print.tif |
pi-craft verify --size --alpha (png) |
| 4 | Brand sheet | DesignCraft | logo + name → 04-sheet/sheet.pdf |
pi-craft verify --pages --text-contains |
| 5 | Package | PdfCraft | sheet → 05-package/brand-kit.pdf |
pi-craft verify --pages --text-contains |
Hand-off formats: svg between vector steps (+ pdf for print), png with alpha for screens, tiff for print, pdf for
delivery. An svg is never passed to pi-craft verify (it has no vector probe): gate its png preview
(vectorcraft-cli convert x.svg x.png --scale N, then --size). --alpha is asserted on png only.
Step 0 — Preflight and job
Output: craft-jobs/<slug>/job.json (created or loaded).
Gate: check: job.
| Sibling | Package | Check | If missing |
|---|---|---|---|
anti-slop-brandkit |
@blackbelt-technology/anti-slop-frontend |
skill in the loaded skill list | opt-in only: used solely on an explicit user request, after approval — see Generated concepts (opt-in); without it the user supplies a logo |
pi-nano-banana |
already a dependency of craft-apps | usable credentials (only relevant to the opt-in branch) | no credentials: tell the user and offer to start from a user-supplied logo file |
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.
- 3d ago First seen · 185 lines · 88 tokens per session scan A d42cebaf9b34
craft-brand-kit is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (326 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 3,194 once invoked, about $0.0004 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-18.
Other skills, from other repositories
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-plan-by-design
Compile a design document into a ralphex execution plan.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.