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 commands/rhuss/cc-spex/update-superpowersgit clone --depth 1 https://github.com/rhuss/cc-spexWrote 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/commands/rhuss/cc-spex/update-superpowers)<a href="https://agentmods.dev/commands/rhuss/cc-spex/update-superpowers"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/update-superpowers.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 | $0.00016 | $0.02811 |
| Opus 5 | $0.00008 | $0.01406 |
| Sonnet 5 | $0.00003 | $0.00562 |
| Haiku 4.5 | $0.00002 | $0.00281 |
Grade C, and why
update-superpowers scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf $TEMP_DIR How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upstream Superpowers Sync Workflow
Purpose: Sync modified skills with upstream superpowers while preserving spex enhancements.
Context: This command is for maintaining the cc-spex plugin, not for end users.
Safety Check
Before proceeding, verify we're in the plugin development directory:
# Check for plugin marker
if [ ! -f "spex/.superpowers-sync" ] || [ ! -f "spex/.claude-plugin/plugin.json" ]; then
echo "ERROR: This command only works in cc-spex plugin directory"
echo "Current directory: $(pwd)"
exit 1
fi
# Verify we're in the right repo
if ! grep -q "cc-spex" spex/.claude-plugin/plugin.json 2>/dev/null; then
echo "ERROR: This doesn't appear to be the cc-spex repository"
exit 1
fi
echo "Plugin directory confirmed"
If checks fail, STOP and inform user this command is only for plugin maintenance.
Pre-Sync Preparation
1. Load Current Sync State
cat spex/.superpowers-sync
Extract:
last_sync_commit: Last upstream commit we synced frommodified_skills: Which skills are modified and howupstream_repo: Upstream repository URL
2. Clone/Update Upstream Repository
# Create temp directory
TEMP_DIR=$(mktemp -d)
cd "$TEMP_DIR"
# Clone upstream
git clone https://github.com/obra/superpowers superpowers-upstream
cd superpowers-upstream
# Get current HEAD
CURRENT_COMMIT=$(git rev-parse HEAD)
CURRENT_DATE=$(git log -1 --format=%cd --date=short)
echo "Upstream HEAD: $CURRENT_COMMIT ($CURRENT_DATE)"
3. Check What Changed
For each modified skill, get the diff:
LAST_SYNC=$(jq -r '.last_sync_commit' spex/.superpowers-sync)
# For each modified skill
for skill in writing-plans code-review verification-before-completion brainstorming; do
UPSTREAM_FILE="skills/${skill}/SKILL.md"
# Get changes since last sync
if [ "$LAST_SYNC" != "INITIAL" ]; then
echo "=== Changes to $skill ==="
git log --oneline $LAST_SYNC..HEAD -- "$UPSTREAM_FILE"
echo ""
else
echo "=== $skill (INITIAL SYNC) ==="
echo "Will use current upstream version as baseline"
echo ""
fi
done
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.
- 4d ago First seen · 373 lines · 16 tokens per session scan C 1abefc597176
update-superpowers is a command published in the GitHub repository rhuss/cc-spex (114 stars, last pushed 15d ago), licensed Apache-2.0. It adds 16 tokens to every session and 2,811 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.