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/dtyq/magic/ai-card-generatornpx skills add dtyq/magic --skill ai-card-generatorgit clone --depth 1 https://github.com/dtyq/magicWrote 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/dtyq/magic/ai-card-generator)<a href="https://agentmods.dev/skills/dtyq/magic/ai-card-generator"><img src="https://agentmods.dev/badge/skills/dtyq/magic/ai-card-generator.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.1 | $0.00121 | $0.04968 |
| Opus 5 | $0.00060 | $0.02484 |
| Sonnet 5 | $0.00024 | $0.00994 |
| Haiku 4.5 | $0.00012 | $0.00497 |
Grade A, and why
ai-card-generator 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 6d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
13 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.
- references/card-spec.md 11 KB
- templates/analytics-panel/index.html 12 KB
- templates/analytics-panel/prompts/deep-analysis.txt 419 B
- templates/analytics-panel/scripts.js 9.9 KB runs code
- templates/analytics-panel/styles.css 8.8 KB
- templates/daily-digest/index.html 15 KB
- templates/daily-digest/prompts/deep-analysis.txt 451 B
- templates/daily-digest/scripts.js 5.6 KB runs code
- templates/daily-digest/styles.css 9.2 KB
- templates/hotspot-tracker/index.html 13 KB
- templates/hotspot-tracker/prompts/deep-analysis.txt 515 B
- templates/hotspot-tracker/scripts.js 8.1 KB runs code
- templates/hotspot-tracker/styles.css 9.5 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.
- 6d ago First seen · 417 lines · 121 tokens per session scan A 001f1092bb35
ai-card-generator is a skill published in the GitHub repository dtyq/magic (5,015 stars, last pushed 24d ago), with no licence file. It adds 121 tokens to every session and 4,968 once invoked, about $0.0006 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-30.
Other skills, from other repositories
pptx
Create and validate Microsoft PowerPoint presentations (.pptx), including structured slide decks, tables, workflows, metadata, and reproducible generation scripts. Use for presentation, slides, PowerPoint, PPT, or PPTX creation and verification tasks.
frontend-code-review
Use only when the user explicitly requests a review or audit of frontend code under web/ or packages/dify-ui/. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, or backend-only code.
how-to-write-component
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or interaction ownership. Do not use for review-only requests, test-only work, copy-only edits, or styling-only changes.
backend-code-review
Use only when the user explicitly requests a review or audit of backend code under api/. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend code outside api/.
e2e-cucumber-playwright
Use when writing, changing, or reviewing Cucumber and Playwright tests under e2e/, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for Vitest, React Testing Library, backend tests, or generic browser automation outside the E2E suite.
frontend-testing
Use when writing or changing Vitest or React Testing Library tests under web/ or packages/dify-ui/, or when the user explicitly requests frontend test strategy, including evaluation of an existing strategy. Do not use for frontend code-review-only requests, general testability discussion, Python tests, or…