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 whateverforever/maxs-claude-skills --skill anki-cardsgit clone --depth 1 https://github.com/whateverforever/maxs-claude-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/whateverforever/maxs-claude-skills/anki-cards)<a href="https://agentmods.dev/skills/whateverforever/maxs-claude-skills/anki-cards"><img src="https://agentmods.dev/badge/skills/whateverforever/maxs-claude-skills/anki-cards/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/whateverforever/maxs-claude-skills/anki-cards"><img src="https://agentmods.dev/badge/skills/whateverforever/maxs-claude-skills/anki-cards.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.00137 | $0.02440 |
| Opus 5 | $0.00068 | $0.01220 |
| Sonnet 5 | $0.00027 | $0.00488 |
| Haiku 4.5 | $0.00014 | $0.00244 |
Grade A, and why
anki-cards 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anki Flashcard Generator
Turn conversation content into high-quality Anki flashcards, exported as a TSV file ready for import.
Workflow
1. Gather Parameters
When the user asks for Anki cards, ask two things before generating:
-
How many cards? — Ask for a target number. If the conversation is short, suggest a reasonable range (e.g., "This conversation covered ~3 key topics — I'd suggest 5–10 cards. How many would you like?").
-
One-sided or double-sided? — Default suggestion is one-sided. Briefly explain the double-sided option:
- One-sided (default): Front = question, Back = answer.
- Double-sided: Both sides are questions. Knowing either side lets you recall the other. Example:
- Front: "What flag has red crosses on a white background?"
- Back: "How does the flag of Georgia look?"
2. Extract Key Facts from the Conversation
Review the conversation and identify the facts, concepts, distinctions, and relationships that the user would benefit from memorizing. Focus on:
- New information the user learned (things they asked about or expressed surprise at)
- Core concepts and definitions
- Key distinctions or comparisons discussed
- Concrete facts (names, numbers, dates, formulas, commands)
- Cause-and-effect relationships
- Corrections or misconceptions that were cleared up
Ignore: pleasantries, meta-discussion about the conversation itself, tangential remarks, and anything the user clearly already knew.
3. Write Cards Following Best Practices
Every card must follow these principles:
Minimum Information Principle
Each card tests exactly one atomic fact or association. Never combine multiple facts into a single card.
- BAD: "What are the three types of heat transfer?" → "Conduction, convection, and radiation"
- GOOD: Three separate cards, each asking about one type, or each asking what category a given type belongs to.
No Orphan Cards
Every card must contain enough context to be understood in isolation, months later, without remembering the original conversation. Add brief context cues where needed.
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.
- 11d ago First seen · 174 lines · 137 tokens per session scan A 6259a51f7497
anki-cards is a skill published in the GitHub repository whateverforever/maxs-claude-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 137 tokens to every session and 2,440 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
rwkv-architecture
RNN+Transformer hybrid with O(n) inference. Linear time, infinite context, no KV cache. Train like GPT (parallel), infer like RNN (sequential). Linux Foundation AI project. Production at Windows, Office, NeMo. RWKV-7 (March 2025). Models up to 14B parameters.
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
explain-this
Explain whatever the user is pointing at right now in plain language: a pending question, a piece of code, an error, a command output, or an artifact like a plan or findings report. Use when the user asks to "explain this", "what am I being asked", "what's happening right now", "help me understand this", "what does…
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
understand-change
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed"…