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 martineserios/thebrana --skill impeccablegit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/impeccable)<a href="https://agentmods.dev/skills/martineserios/thebrana/impeccable"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/impeccable/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/martineserios/thebrana/impeccable"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/impeccable.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.00189 | $0.02466 |
| Opus 5.5 | $0.00076 | $0.00986 |
| Sonnet 5.5 | $0.00038 | $0.00493 |
| Haiku 4.5 | $0.00019 | $0.00247 |
Grade A, and why
impeccable 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.
This is a copy
94% identical to impeccable — 48 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill gives you the tools and permission to create design that earns to be called out-of-distribution craft: Whereas before, your design work would have been safe, timid and measured, you now approach every design task as a award-winning design director with impeccable understanding for what makes exceptional design work: production-grade code, peak creativity, a clear POV, deep understanding of the needs of the client and users, and exceptional craft.
Core principles:
- Go all out. No hedging, no shortcuts. The deliverable must be complete (except assets the user must provide).
- Dream big and bold. Distinct, beautiful, outstanding and highly inspiring work.
- Verify in bounded passes, not a loop, and the ceiling covers the whole cycle: screenshots, defect scans, micro-edits, and rebuilds alike. Build fully, inspect once with a batched round (desktop and mobile together on the web; the shipped device classes on a native platform), fix everything it shows in one batch, confirm with at most one more round, and stop polishing. Open-ended self-QA burns the user's money doing worse what the finish handoffs do better.
Setup
- Run
node <skill-base-dir>/scripts/context.mjsonce per session, where<skill-base-dir>is the loaded base directory the runtime reports for this skill; keep cwd at the user's project. That base directory resolves everynode .agents/skills/impeccable/scripts/...command in this skill and its references, and.agents/skills/impeccable/scriptsis the fallback only when the runtime reports no base directory. Pass a named source file or route as--target <path>. It loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it. - Before acting, load the one playbook that owns the request: the Commands table's reference for an explicit or clearly implied sub-command, or reference/new-work.md for a new surface or replacement visual world. Then inspect the target and at least one representative source of incumbent visual truth (tokens, theme, CSS, component, or asset) before editing.
- After analysis and direction are resolved, load reference/craft-floor.md immediately before editing UI. It carries the quality floor, the absolute bans, and the reflexes no detector catches. Do not load it for planning-only work.
What ships with it
39 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.
- reference/adapt.md 10 KB
- reference/adapt.native.md 3.8 KB
- reference/android.md 4.0 KB
- reference/animate.md 5.1 KB
- reference/audit.md 7.7 KB
- reference/audit.native.md 8.2 KB
- reference/bolder.md 3.5 KB
- reference/clarify.md 4.5 KB
- reference/colorize.md 4.4 KB
- reference/craft-floor.md 5.1 KB
- reference/craft.md 555 B
- reference/critique.md 42 KB
- reference/degraded/asset-producer.md 10 KB
- reference/degraded/documenter.md 3.3 KB
- reference/degraded/finish-reviewer.md 11 KB
- reference/degraded/manual-edit-applier.md 7.0 KB
- reference/delight.md 3.6 KB
- reference/distill.md 5.6 KB
- reference/doctor.md 4.6 KB
- reference/document.md 27 KB
- reference/extract.md 3.4 KB
- reference/harden.md 8.3 KB
- reference/hooks.md 12 KB
- reference/init.md 8.7 KB
- reference/ios.md 3.7 KB
- reference/layout.md 5.0 KB
- reference/live-setup.md 7.2 KB
- reference/live.md 35 KB
- reference/new-work.md 37 KB
- reference/onboard.md 7.6 KB
- reference/operate.md 4.0 KB
- reference/optimize.md 7.4 KB
- reference/overdrive.md 8.7 KB
- reference/polish.md 5.5 KB
- reference/quieter.md 4.8 KB
- reference/routing.md 2.8 KB
- reference/shape.md 3.5 KB
- reference/typeset.md 5.1 KB
- reference/visualize.md 13 KB
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 · 87 lines · 189 tokens per session scan A 9b5991c63307
impeccable is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 189 tokens to every session and 2,466 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to impeccable, differing in 48 lines, and is treated as a copy.
Other skills, from other repositories
design-critic
Designer senior extremamente critico. Analisa aplicacao web em 5 pilares (Visual Consistency, Information Hierarchy, Interaction Quality, Spatial Design, Polish & Craft), captura screenshots via Playwright, gera relatorio com score, e aplica auto-fix em todos os findings. Triggers on: design audit, design review…
carrier-product-review
A product-review guide for telecommunications products such as mobile apps, service plans, billing systems, and customer or business platforms.
interface-auditor
Detect UX antipatterns (smells) in interface descriptions using the uxuiprinciples smell taxonomy. Returns structured findings with matched symptoms, severity, and step-by-step remediation recipes. API key optional — full remediation recipes require uxuiprinciples.com API Access.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
design
Use when designing, redesigning, restyling or reviewing a web page or app screen (landing, product site, portfolio, dashboard, docs) or when a UI looks generic or AI-made. Deals a researched direction, takes the idea from the subject, uses real pictures, proves it in a browser. NOT the words (landing-copy), NOT…
prism-ui
Implement a complete UI screen or feature from a Form visual spec. Use when asked to "build a page", "implement this screen", "build the frontend for this feature", or "create this UI".