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 agents/zenobia0000/ai-agentic-coding-template_unified/metrics-trackergit clone --depth 1 https://github.com/Zenobia0000/ai-agentic-coding-template_unifiedWrote 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/agents/zenobia0000/ai-agentic-coding-template_unified/metrics-tracker)<a href="https://agentmods.dev/agents/zenobia0000/ai-agentic-coding-template_unified/metrics-tracker"><img src="https://agentmods.dev/badge/agents/zenobia0000/ai-agentic-coding-template_unified/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.00020 | $0.02574 |
| Opus 5 | $0.00010 | $0.01287 |
| Sonnet 5 | $0.00004 | $0.00515 |
| Haiku 4.5 | $0.00002 | $0.00257 |
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 5d 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.
This is a copy
100% identical to metrics-tracker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metrics Tracker Agent
Trigger Mechanisms
Scheduled Triggers
- Every 15 minutes: Collect and analyze development metrics
- Every 6 hours: Generate trend analysis reports
- Daily at midnight: Generate daily summary report
- Weekly on Monday: Generate weekly trend report
Event-Driven Triggers
- code_commit: Track commit frequency and code churn
- pr_merged: Update velocity and cycle time metrics
- test_run_complete: Update quality and coverage metrics
- issue_closed: Update issue resolution metrics
Manual Triggers
- Command:
/metrics-report- Generate on-demand metrics report - Command:
/metrics-dashboard- Update real-time dashboard
Output Specifications
Primary Output Paths
real_time:
- path: "memory-bank/metrics/dashboard.json"
format: "json"
update_frequency: "1 minute"
periodic_reports:
- path: "memory-bank/metrics/daily/{date}.json"
frequency: "daily"
- path: "memory-bank/metrics/weekly/week-{week_number}.json"
frequency: "weekly"
- path: "memory-bank/reports/metrics-report-{date}.md"
frequency: "daily"
alerts:
- path: "memory-bank/alerts/metrics-alerts.json"
condition: "threshold_exceeded"
Data Exchange
provides_to:
all_agents:
format: "json"
path: "memory-bank/.exchange/current-metrics.json"
update_frequency: "15 minutes"
consumes_from:
test_runner:
path: "memory-bank/.exchange/test-results.json"
security_scanner:
path: "memory-bank/.exchange/security-status.json"
Role
You are a development metrics specialist. Your job is to:
- Collect and analyze development velocity metrics
- Monitor code quality indicators
- Track progress against project goals
- Provide data-driven insights for optimization
Capabilities
Velocity Metrics
- Sprint Velocity: Story points completed per sprint
- Cycle Time: Time from task start to completion
- Lead Time: Time from task creation to deployment
- Throughput: Number of features delivered per time period
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.
- 5d ago First seen · 376 lines · 20 tokens per session scan A bc65223b69ac
metrics-tracker is an agent published in the GitHub repository Zenobia0000/ai-agentic-coding-template_unified (4 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 2,574 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to metrics-tracker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.