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 JNZader/repoforge --skill skill-powerupsgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/skill-powerups)<a href="https://agentmods.dev/skills/jnzader/repoforge/skill-powerups"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/skill-powerups/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/jnzader/repoforge/skill-powerups"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/skill-powerups.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.00057 | $0.00481 |
| Opus 5 | $0.00028 | $0.00241 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
skill-powerups 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.
What it actually says
Purpose
Transform static SKILL.md docs into interactive learning. Power-ups teach skills step-by-step with real examples, exercises, and knowledge checks.
Invocation
/powerup <skill-name> # full tutorial
/powerup <skill-name> --quick # key concepts only
/powerup <skill-name> --test # knowledge check only
Power-Up Flow
Step 1: Introduction
- What you'll learn (3 bullets)
- Estimated time
- Prerequisites
Step 2: Concept Modules (one per core concept)
For each concept:
- The Problem: Why it matters
- The Pattern: Correct approach with real code
- Anti-Pattern: What NOT to do
- Try It: Small exercise
- Check: Verify they got it right
Step 3: Knowledge Check
3-5 multiple choice questions from the concepts.
Step 4: Summary
Key takeaways + link to full SKILL.md.
Generating from SKILL.md
When no POWERUP.md exists, dynamically generate:
- Read SKILL.md
- Extract: Purpose, Rules, Examples, Anti-Patterns
- Convert each Critical Rule into a module
- Generate knowledge check questions
- Present interactively
Critical Rules
- Power-ups are ALWAYS interactive — ask, wait, give feedback
- Use real project code examples when possible
- Keep each module under 2 minutes
- ALWAYS end with a knowledge check
- If user gets a question wrong, explain WHY before continuing
- Never skip anti-patterns — knowing what NOT to do is critical
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 · 74 lines · 57 tokens per session scan A 0dcc7f4aae4c
skill-powerups is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 15d ago), licensed MIT. It adds 57 tokens to every session and 481 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
socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than…
take-notes
Turn a YouTube video, a web article, or several sources at once into one set of didactic study notes, written as a self-contained HTML page under /take-notes/htmlreports and opened in the browser.
learning-mode
Turn a regular Claude Code session into a learn-by-doing coding tutorial. The user keeps shipping real work, but at deliberate moments Claude hands off a focused chunk for the user to write by hand, then reviews it. Maintains a per-repo learning plan and a spaced-repetition log under .claude/learning/ so topics…
simplicio-learn
Persist what a run taught you so the next run is cheaper and more correct — mine high-signal lessons from the trajectory, dedup them, and write them back to AGENTS.md / memory so they're applied not re-derived. Use after a run or at session end, when the user says "remember this", "do a retrospective", "learn from…
explainer-site
Create "How X Works" deep-dive explainer websites with the curious, technical-but-accessible style of howkeyboardswork.com. Use when asked to explain how something works, create an educational single-page guide, or build an interactive explainer site on any topic.
onboard-our-stack
Onboard a newcomer to THIS codebase, or answer a targeted "how does our X work" question, by walking curated reading lists and synthesizing the mental model — never by guessing. Works out of the box: with a committed .claude/onboard/topics.yaml it walks that curated path; without one it cold-starts from the repo's own…