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 skills/samibs/skillfoundry/metricsnpx skills add samibs/skillfoundry --skill metricsgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00004 | $0.04517 |
| Opus 5 | $0.00002 | $0.02259 |
| Sonnet 5 | $0.00001 | $0.00903 |
| Haiku 4.5 | $0.00000 | $0.00452 |
Grade B, and why
metrics scanned grade B 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SUCCESS_RATE=$(cat .claude/metrics.json | jq '.summary.success_rate') How it starts
The opening of the file, as written. The whole thing — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metrics Dashboard
View and analyze execution metrics for the Claude AS framework.
OPERATING MODE
/metrics → Show metrics dashboard
/metrics agents → Agent performance breakdown
/metrics stories → Story completion analysis
/metrics errors → Error analysis and patterns
/metrics trends → Trend analysis over time
/metrics export [format] → Export metrics (json/csv/md)
/metrics reset → Reset metrics (with confirmation)
DASHBOARD VIEW
On /metrics invocation, display the comprehensive dashboard:
METRICS DASHBOARD
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PROJECT: [project-name]
PERIOD: All time (since [start-date])
QUICK STATS
┌────────────────────────────────────────────────────────────────┐
│ Executions: [N] │ Success: [X]% │ Stories: [N] │ Tokens: [X]K │
└────────────────────────────────────────────────────────────────┘
RECENT ACTIVITY (Last 7 days)
├── Executions: [N]
├── Stories Completed: [N]
├── Success Rate: [X]%
└── Avg Tokens/Execution: [X]K
TOP PERFORMING AGENTS
1. [agent-name]: [X]% success ([N] calls)
2. [agent-name]: [X]% success ([N] calls)
3. [agent-name]: [X]% success ([N] calls)
ATTENTION NEEDED
[List any metrics below threshold]
Use /metrics [category] for detailed breakdowns.
AGENT METRICS
On /metrics agents:
AGENT PERFORMANCE METRICS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OVERVIEW
┌──────────────────┬──────────┬──────────┬──────────┬──────────┬──────────┐
│ Agent │ Calls │ Success │ Partial │ Failed │ Avg Tok │
├──────────────────┼──────────┼──────────┼──────────┼──────────┼──────────┤
│ ruthless-coder │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
│ ruthless-tester │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
│ gate-keeper │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
│ cold-architect │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
│ docs-codifier │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
│ debug-hunter │ [N] │ [X]% │ [X]% │ [X]% │ [X]K │
└──────────────────┴──────────┴──────────┴──────────┴──────────┴──────────┘
PERFORMANCE RANKING
1. 🥇 [agent]: [X]% success rate
2. 🥈 [agent]: [X]% success rate
3. 🥉 [agent]: [X]% success rate
TOKEN EFFICIENCY
Most Efficient: [agent] ([X] tokens/call avg)
Least Efficient: [agent] ([X] tokens/call avg)
RECENT FAILURES BY AGENT
┌──────────────────┬──────────┬────────────────────────────────────┐
│ Agent │ Failures │ Common Cause │
├──────────────────┼──────────┼────────────────────────────────────┤
│ [agent] │ [N] │ [most common error type] │
└──────────────────┴──────────┴────────────────────────────────────┘
RECOMMENDATIONS
[Based on agent performance, suggest improvements]
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.
- 2d ago First seen · 540 lines · 4 tokens per session scan B e35e6dc02501
metrics is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 4,517 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…