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 andreaswasita/copilot-agents-dojo --skill using-superpowersgit clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/using-superpowers)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/using-superpowers"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/using-superpowers.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 121 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00016 | $0.01782 |
| Opus 5 | $0.00008 | $0.00891 |
| Sonnet 5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
using-superpowers 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 8d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Superpowers Skill
Loads the dojo framework at session start: confirms the core disciplines are active, surfaces relevant lessons, and verifies clean state before any work begins. Does NOT replace the underlying skills — it sequences their loading and the session opening ritual.
When to Use
- At the start of every new session in a dojo-enabled repo.
- When the user says "use superpowers", "activate the dojo", or "start the framework".
- When another skill references the mandatory workflow.
- After resuming from a checkpoint or context handoff.
- NOT mid-session for already-active skills — re-loading wastes turns.
Prerequisites
- The dojo is installed in the repo (
skills/,optional-skills/,tasks/,spec/). - The
view,edit,grep, andpowershellCopilot tools. gitavailable to inspect branch + working tree.tasks/lessons.mdexists (created empty if first session).scripts/verify.sh(orscripts/run-checks.ps1) available for the session-start gate.
How to Run
1. Review `tasks/lessons.md` for relevant active lessons.
2. Open `tasks/todo.md` — is there work in progress?
3. Confirm `git status`: right branch, clean tree (or known WIP).
4. Acknowledge: "Dojo framework active. Core disciplines loaded."
5. Hand off to the trigger skill for the user's actual request.
Quick Reference
| Always-on (core) | Why it loads at every session |
|---|---|
behavioral-foundation |
The five non-negotiable prime directives |
plan-before-code |
Forces planning before any multi-step work |
verify-before-done |
Evidence required for any "done" claim |
self-improvement |
Lessons captured every correction |
demand-elegance |
Hacky solutions get challenged |
autonomous-bug-fix |
Full bug cycle without hand-holding |
safety-guardrails |
Destructive commands get a preflight check |
subagent-strategy |
Delegation is a first-class option |
| Workflow chain (practical) | Triggered when |
|---|---|
brainstorming → plan-before-code → executing-plans → requesting-code-review → finishing-a-development-branch |
A non-trivial change begins |
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.
- 8d ago First seen · 161 lines · 16 tokens per session scan A 30fb55dad857
using-superpowers is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (51 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,782 once invoked, about $0.0001 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
client-onboarding
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is customer-support), NOT renewals/churn past the…
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.
truth-first
A set of rules for writing technical conclusions and performing irreversible or state-changing operations. It requires evidence tied to file and line locations and restricts unsupported claims.
om-system-extension
Extend installed Open Mercato modules through UMES enrichers, interceptors, mutation guards, widgets, menus, entity extensions, events, component/page replacements, and overrides. Use for "extend core", "add field/column/action", "hide page", "intercept API", "UMES", or "rozszerz moduł".