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 sidtheone/tarot-skills --skill moongit clone --depth 1 https://github.com/sidtheone/tarot-skillsWrote 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/sidtheone/tarot-skills/moon)<a href="https://agentmods.dev/skills/sidtheone/tarot-skills/moon"><img src="https://agentmods.dev/badge/skills/sidtheone/tarot-skills/moon/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/sidtheone/tarot-skills/moon"><img src="https://agentmods.dev/badge/skills/sidtheone/tarot-skills/moon.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.00145 | $0.01859 |
| Opus 5 | $0.00072 | $0.00929 |
| Sonnet 5 | $0.00029 | $0.00372 |
| Haiku 4.5 | $0.00015 | $0.00186 |
Grade A, and why
moon 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 9d 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.
- 9d ago First seen · 92 lines · 145 tokens per session scan A 9e1013418844
moon is a skill published in the GitHub repository sidtheone/tarot-skills (2 stars, last pushed 5mo ago), with no licence file. It adds 145 tokens to every session and 1,859 once invoked, about $0.0007 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
lov-fix-until-no-error
A verification-focused debugging workflow that repeatedly runs specified checks, fixes the highest-priority failure, and stops when the checks pass or a genuine external blockage remains.
launch-check
Run a pre-demo/pre-launch audit of the app - test data, broken screens, missing error states, brand consistency. Use when asked to 'demo check', 'launch check', 'pre-demo audit', 'check before user interview', 'audit before demo'.
audio-verification
Verify and debug synthesized audio (Web Audio API) by rendering it offline and measuring the samples, instead of guessing from code or claiming it works untested. Use whenever building, changing, or reviewing UI sound effects, tones, synths, or any AudioContext graph — and especially when sound is reported as…
tdd
TDD workflow - red-green-refactor per docs/methodology/tdd.md. Use when asked to '/tdd', 'TDD workflow', 'red-green-refactor', 'test-first development', 'write the failing test first'.
loop-engineering
Use when designing, orchestrating, or executing autonomous multi-agent coding loops with financial budget caps, minimal fixes, and continuous dev-QA gates.
playwright-qa
Drive the running app with Playwright to verify UI work — act, screenshot, read the screenshot, decide. Use whenever a change is visible or interactive, whenever a UI bug is reported, and instead of reasoning about what the UI probably does.