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-demo-fixture/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-demo-fixture)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-demo-fixture"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-demo-fixture/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-demo-fixture"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-demo-fixture.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.00056 | $0.00473 |
| Opus 5 | $0.00028 | $0.00236 |
| Sonnet 5 | $0.00011 | $0.00095 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
tell-demo-fixture 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.
What it actually says
Tell demo fixtures
Scope
fixtures/generic-app/— deliberately bland demo input (not product code)fixtures/reports/capture.json— committed capture artifactfixtures/reports/tell-report.json— offline demo fallbackCONTRIBUTIONS.md— attribution separating our work from demo input
Planted tells (must trigger)
Genericness: Inter/system font, violet-pink hero gradient, identical card shadows, monotone 8px radius, acid accent on dark bg, emoji in chrome, centered sections, gray mush
Drift: near-duplicate grays, missing focus rings, type scale drift, spacing off 4px grid, state gaps
Intentional: brutalist/mono route or flagged section for intentional taste verdict
Regeneration workflow
- Change fixture UI in
fixtures/generic-app - Run
pnpm dev:fixtureandpnpm capture:fixture - Run
pnpm diagnose:fixtureif full report must update - Update detector golden tests if expectations shift
- Commit
capture.jsonandtell-report.jsontogether
Demo reliability
- Live capture first; offline artifact always works
- If capture/API fails, web returns committed
tell-report.jsonwith clear non-live state - Record backup demo video for reviewer presentation
Build sprint compliance
- Generic app is labeled demo input in
CONTRIBUTIONS.md - Lead demo with capture → diagnose → art-direct → reconcile loop, not KPI cards
- Public repo; only in-event work presented as original contribution
DoD
- ≥8 planted findings on fixture (4 tells + 4 drifts minimum)
- Offline report loads when live path fails
- Fixture remains intentionally bland
Related
- Rules:
.cursor/rules/tell-fixtures.mdc - Agent:
.cursor/agents/fixture-smith.md - BUILD.md §7
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 · 54 lines · 56 tokens per session scan A 19f862556cec
tell-demo-fixture is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 473 once invoked, about $0.0003 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
visual-validation
Autonomous screenshot verification — captures, compares, and AI-evaluates UI changes for visual regressions.
ui-aqa-flow
Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser or Playwright.
agent-gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
dev-testing
A testing guide that defines when to use unit, integration, API, and end-to-end tests. Unit tests check small pieces of code, while end-to-end tests check a full user flow.