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 agentmods add skills/ashishpatill/tell-proof/responsive-performancenpx skills add ashishpatill/tell-proof --skill responsive-performancegit 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/responsive-performance)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/responsive-performance"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/responsive-performance.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 | $0.00064 | $0.00406 |
| Opus 5 | $0.00032 | $0.00203 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
responsive-performance 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 4d 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
responsive-performance
Always-on for every site build. Parent: premium-content-custom-web. Engine always
routes this node via routeSkills. Agents must execute it — not only list it.
Full playbook: agent-skills/web-design/premium-content-custom-web/responsive-performance/SKILL.md
Non-negotiables (auto-apply)
- WebP at display size — after adding photography under
apps/web/public/**, runpnpm media:site(orpnpm media:webp). Hero ≤1600w @q82; editorial ≤1200w; other ≤1000w. Prefer pruning superseded jpg/png (--prune). - Use
SiteImg(apps/web/src/components/site-media/SiteImg.tsx) for specimen media — rewrites.jpg/.png→.webp, setswidth/height,loading,fetchPriority,decoding. - LCP — one priority/eager hero image max; everything else lazy + async decode.
- CLS — always reserve intrinsic width/height; never un-sized
<img>. - Mobile-first — stack grids under ~800px; no autoplay video heroes.
- No heavy formats on the hot path — no multi-MB JPEG heroes in commits.
Verify
pnpm media:site -- --prune
# HTML should reference .webp; public/** should not keep hot-path multi-MB jpg after prune
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.
- 4d ago First seen · 35 lines · 64 tokens per session scan A 34f51d6aa88b
responsive-performance is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 406 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-08-31.
Other skills, from other repositories
miniprogram-development
WeChat Mini Program development skill for building, debugging, previewing, testing, publishing, optimizing, and promoting mini program projects. This skill should be used when users ask to create, develop, modify, debug, preview, test, deploy, publish, launch, review, optimize, or promote WeChat Mini Programs, mini…
firebase-app-check
Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.
flutter-app-architecture
Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).
firebase-ai
Use when setting up firebaseai, generating text/chat with Gemini, streaming AI output, building multimodal prompts, or handling AI errors.
firebase-storage
Use when setting up Storage, uploading/downloading files, managing metadata, handling errors, or applying security rules.
auth-wechat-miniprogram
CloudBase WeChat Mini Program native authentication guide. This skill should be used when users need mini program identity handling, OPENID/UNIONID access, or wx.cloud auth behavior in projects where login is native and automatic.