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/mu4farooqi/superwiser/statsgit clone --depth 1 https://github.com/mu4farooqi/superwiserWrote 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/mu4farooqi/superwiser/stats)<a href="https://agentmods.dev/commands/mu4farooqi/superwiser/stats"><img src="https://agentmods.dev/badge/commands/mu4farooqi/superwiser/stats.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.00006 | $0.00259 |
| Opus 5 | $0.00003 | $0.00130 |
| Sonnet 5 | $0.00001 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
stats 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 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.
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
Show statistics about captured rules and API token usage.
Instructions
Call the get_stats MCP tool from superwiser.
Present the results in a readable format:
- Show total rule count
- Display pending conflicts if any (only if non-zero)
- Show pending/processing/failed queue counts (only if non-zero)
- Show token usage: today and last 7 days with daily average
- Show breakdown by operation (discovery vs extraction)
Example output format:
Rule Statistics:
- Total rules: 47
- Pending conflicts: 2
- Queue: 3 pending, 1 processing
Token Usage:
Today: 57,730 tokens (8 calls)
Input: 38,420 | Output: 6,810
Last 7 Days: 312,450 tokens (67 calls)
Daily avg: 44,635 tokens
By Operation (7d):
Discovery: 125,000 tokens (12 calls)
Extraction: 187,450 tokens (55 calls)
If there are failed items, show: "- Failed: 2 (check worker logs)" If token_usage has an error, show: "Token tracking: Not yet initialized"
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 · 40 lines · 6 tokens per session scan A 4b61eeb95647
stats is a command published in the GitHub repository mu4farooqi/superwiser (6 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 259 once invoked, about $0.0000 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 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.