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 qhuang20/shazam --skill design-an-interfacegit clone --depth 1 https://github.com/qhuang20/shazamWrote 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/qhuang20/shazam/design-an-interface)<a href="https://agentmods.dev/skills/qhuang20/shazam/design-an-interface"><img src="https://agentmods.dev/badge/skills/qhuang20/shazam/design-an-interface/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/qhuang20/shazam/design-an-interface"><img src="https://agentmods.dev/badge/skills/qhuang20/shazam/design-an-interface.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.00043 | $0.00743 |
| Opus 5.5 | $0.00017 | $0.00297 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
design-an-interface 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 99 lines · 43 tokens per session scan A 0441f73919df
design-an-interface is a skill published in the GitHub repository qhuang20/shazam (4 stars, last pushed 6mo ago), with no licence file. It adds 43 tokens to every session and 743 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
django-components
Django version facts, where to fetch exact API details, and pitfalls that cause real bugs (N+1, signals, async ORM, transactions, migrations, settings, security). Use for any Django model, view, form, admin, auth, cache, or deploy work.
image-annotate
Marks up an existing image with arrows, boxes, text, numbered steps, highlights, blur, or redaction, and saves a new PNG or JPEG. Use to annotate a screenshot, add callouts, or redact secrets before sharing.
symfony-components
Opinionated defaults, version facts, and pitfalls for Symfony and its components. Use when writing, reviewing, or upgrading Symfony code, to match the installed version's API and avoid known traps.
api-design
REST and GraphQL API design covering resource modeling, status codes, error contracts, pagination, versioning, and evolution. Use to design or review an API.
doctrine-orm
Doctrine ORM 3 and DBAL 4 in Symfony, with version facts and pitfalls. Use when fixing N+1 or slow Doctrine pages, choosing LAZY, EAGER or fetch joins, ordering migrations, hitting "EntityManager is closed", locking rows, batch imports, or Messenger workers that lose the database connection.
symfony-testing
Symfony tests with PHPUnit 11 to 13: pick KernelTestCase, WebTestCase, ApiTestCase or Panther and avoid version pitfalls. Use when adding a functional test, testing a controller, a service missing from getContainer, mocking the HTTP client or clock, Messenger or mailer assertions, or Foundry and DAMA setup.