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/dokkabei97/forged-claude-code/analytics-scaffoldgit 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/commands/dokkabei97/forged-claude-code/analytics-scaffold)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/analytics-scaffold"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/analytics-scaffold.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.00022 | $0.00775 |
| Opus 5 | $0.00011 | $0.00387 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
analytics-scaffold 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/analytics-scaffold - Event Tracking Code Generator
Triggers
- Setting up product analytics for a new feature
- Standardizing event tracking across the codebase
- Migrating between analytics providers
Usage
/analytics-scaffold [event spec file or description]
/analytics-scaffold --provider mixpanel
/analytics-scaffold --provider ga4
/analytics-scaffold --provider amplitude
Behavioral Flow
Phase 1: Define Event Spec
## Event Specification
| Event Name | Trigger | Properties |
|-----------|---------|------------|
| page_viewed | Page load | page_name, referrer |
| signup_started | Click signup CTA | source, plan_type |
| signup_completed | Account created | method (email/google/github) |
| feature_used | Feature interaction | feature_name, duration_ms |
| upgrade_clicked | Click upgrade | current_plan, target_plan |
Phase 2: Generate Tracking Code
Analytics Wrapper (provider-agnostic):
// lib/analytics.ts
type EventName = 'page_viewed' | 'signup_started' | 'signup_completed'
| 'feature_used' | 'upgrade_clicked'
type EventProperties = {
page_viewed: { page_name: string; referrer?: string }
signup_started: { source: string; plan_type?: string }
signup_completed: { method: 'email' | 'google' | 'github' }
feature_used: { feature_name: string; duration_ms?: number }
upgrade_clicked: { current_plan: string; target_plan: string }
}
export function track<T extends EventName>(
event: T,
properties: EventProperties[T]
): void {
// Provider-specific implementation
if (typeof window !== 'undefined') {
mixpanel?.track(event, properties)
// or: gtag('event', event, properties)
// or: amplitude.track(event, properties)
}
}
export function identify(userId: string, traits?: Record<string, any>): void {
mixpanel?.identify(userId)
mixpanel?.people.set(traits)
}
Usage in Components:
import { track } from '@/lib/analytics'
// In signup form
track('signup_started', { source: 'hero_cta', plan_type: 'free' })
// After successful signup
track('signup_completed', { method: 'google' })
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 · 119 lines · 22 tokens per session scan A cd0527fa6f9b
analytics-scaffold is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 775 once invoked, about $0.0001 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
setup
The user invoked /setup to prepare the Python environment for this repo.
critique-agent
The user invoked /critique-agent.
critique-prd
The user invoked /critique-prd.
start
The user invoked /start.
Icon Product & Policy Review
Intelligent product and policy analysis that automatically selects the most relevant legendary product and policy experts.
checklist
Generate a custom checklist for the current feature based on user requirements.