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 Dokkabei97/forged-claude-code --skill metrics-trackergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/metrics-tracker)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/metrics-tracker"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/metrics-tracker.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.1 | $0.00045 | $0.01258 |
| Opus 5 | $0.00023 | $0.00629 |
| Sonnet 5 | $0.00009 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
metrics-tracker 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metrics Tracker - Startup Metrics Framework
Overview
Defines the right metrics for your startup stage. Measuring everything measures nothing — focus on the metrics that drive decisions.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Defining initial metrics | Stage-based metric selection |
| "KPI", "AARRR" | Metric framework setup |
| Weekly/monthly review | Metric report template |
2. Metrics by Stage
Pre-PMF (Product-Market Fit 전)
Focus: Are users getting value?
| Metric | Definition | Target |
|---|---|---|
| Activation Rate | % of signups completing core action | > 40% |
| Retention (Week 1) | % returning after 7 days | > 25% |
| NPS | Net Promoter Score | > 40 |
| Qualitative feedback | User interview insights | Weekly interviews |
| Sean Ellis Test | "Very disappointed" if product disappeared | > 40% |
Post-PMF
Focus: Can we grow efficiently?
| Metric | Definition | Target |
|---|---|---|
| MRR | Monthly Recurring Revenue | Growing MoM |
| MRR Growth Rate | (This month - Last month) / Last month | > 15% MoM |
| Churn Rate | % of users/revenue lost per month | < 5% |
| CAC | Total acquisition cost / New customers | Decreasing |
| LTV | Avg revenue per customer × Avg lifetime | LTV/CAC > 3 |
Scale
Focus: Is growth sustainable and efficient?
| Metric | Definition | Target |
|---|---|---|
| ARR | Annual Recurring Revenue | Milestone-based |
| Net Revenue Retention | Expansion - Churn | > 110% |
| Payback Period | Months to recover CAC | < 12 months |
| Gross Margin | (Revenue - COGS) / Revenue | > 70% |
| Rule of 40 | Revenue growth % + Profit margin % | > 40% |
3. AARRR Framework
Acquisition → Activation → Retention → Revenue → Referral
[How users [First [Users [Users [Users bring
find you] value come pay] others]
moment] back]
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 · 168 lines · 45 tokens per session scan A 060efb3e9d1c
metrics-tracker is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,258 once invoked, about $0.0002 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
vellum-skills-catalog
Discover bundled skills and search/install community skills from the skills.sh registry.