Borrowing it
Nothing to install: this file belongs to ashishpatill/tell-proof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ashishpatill/tell-proof/master/.cursor/skills/tell-template-craft/SKILL.mdgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/tell-template-craft)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-template-craft"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-template-craft/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/ashishpatill/tell-proof/tell-template-craft"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-template-craft.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.01301 |
| Opus 5 | $0.00044 | $0.00651 |
| Sonnet 5 | $0.00018 | $0.00260 |
| Haiku 4.5 | $0.00009 | $0.00130 |
Grade A, and why
tell-template-craft 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tell template craft (plumbing → designer corridors)
Token-efficient loop for templates. Do not invent layout plumbing from scratch. Do not restyle from named agencies. Two phases, always in this order:
| Phase | Source | Use for |
|---|---|---|
| A — Plumbing | Local peer checkout (research/plumbing-reference.local.json → localCheckout, or /tmp/learn-plumbing/reference) |
Working solutions: landmarks, sticky/opaque nav, focus-visible, reduced-motion, stacking/z-index, overflow, hero claim vs figure collision, state coverage, anti-AI-slop checks |
| B — Craft | Measured corpus + research/aggregate.json + docs/10_DESIGN_EVIDENCE.md |
Composition corridors from top designer / product pages (fold figure, inverse share, display, bleeds) — ids/categories only, never names or URLs in commits |
The peer daemon is not an aesthetic source. Peer theme packs and named studios must not appear in
committed code, comments, docs, or copy. Local study of designer GitHub template repos is allowed
for measurement and eye only; encode results as anonymised corridors (same as design-research-loop).
Never name the peer product in commits. Platform/MCP/auth adaptations: docs/11–docs/13.
When to run
- Creating a new
siteKind/ template / showcase offering - Fixing a visual bug (overlap, ghosting, empty band, clipped type)
- Improving an existing template until satisfactory
- Redesigning
/showcaseor Studio presentation of offerings
Phase A — peer plumbing (do this first)
- Reproduce the bug or blank feature with Playwright (
pnpm research:shots -- --page <id>or a local route screenshot). - Search the peer checkout for a solved pattern, not a look:
craft/anti-ai-slop.md,craft/typography*.md,craft/state-coverage.md,craft/accessibility-baseline.mddesign-templates/*only for structure/HTML landmarks / CSS stacking ideas
- Encode the fix in
@tell/design-skills(orapps/webfor showcase chrome) + add a gate inbasics-checklist.tswhen the failure is repeatable. - Prefer the smallest change that clears the plumbing failure. For labeled hero figures (studio/consumer): stack fold — opaque claim band in document flow, then the figure. Never absolutely overlay stage labels under readable type (Fieldmark collision). Soft-gradient overclaim is fine only when the underlayer has no competing ink.
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.
- 8d ago First seen · 93 lines · 88 tokens per session scan A 62515c7cb708
tell-template-craft is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 16d ago), licensed MIT. It adds 88 tokens to every session and 1,301 once invoked, about $0.0004 per session on Opus 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-03.
Other skills, from other repositories
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
better-design
Build, improve, and review production interfaces with the Better Design MCP. Use for frontend design, UI, UX, interactions, flows, forms, navigation, components, styling, design systems, accessibility, responsive layouts, motion, React Native, Expo, Shopify, Three.js, and product video work, especially when creating…
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…
tw-component
Generate a UI component using correct Tailwind CSS v4 utility classes, CSS variable theming, and accessibility best practices. Prevents v3 syntax hallucination by grounding output in verified v4 patterns.
frontend-design
Create distinctive, production-grade frontend interfaces with intentional aesthetics, high craft, and non-generic visual identity. Use when building or styling web UIs, components, pages, dashboard...