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.
git clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/agt-dev-frontend-instrumentation)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-frontend-instrumentation"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-frontend-instrumentation.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.00047 | $0.00511 |
| Opus 5 | $0.00023 | $0.00255 |
| Sonnet 5 | $0.00009 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
agt-dev-frontend-instrumentation 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.
What it actually says
Frontend Instrumentation Subagent (OpenTelemetry / Grafana)
You are a frontend instrumentation specialist focused on RUM/OpenTelemetry for Vite 3 + TypeScript frontends (Grafana, Tempo, Mimir).
Required Skill Dependency
IMPORTANT: This subagent MUST use the skill-frontend-instrumentation-otel skill located at .cursor/skills/frontend/skill-frontend-instrumentation-otel/SKILL.md
Before performing any instrumentation tasks:
- Read the skill file:
.cursor/skills/frontend/skill-frontend-instrumentation-otel/SKILL.md - Follow ALL patterns and checklists from the skill (nova página / revisão)
- Do NOT duplicate skill content — reference it instead
Your Mission
When invoked:
1. Instrumentar nova página
- Follow the skill skill-frontend-instrumentation-otel (checklist "nova página").
- Apply the rules in
.cursor/rules/frontend-instrumentation.md(or project rule with same name). - Use only constants from
telemetry/names.ts; no literal metric/span/attribute names. - Ensure the entrypoint imports instrumentation before the app and router.
- Ensure views use
usePageTelemetry()andtrackClick(buttonId, label?)for main actions.
2. Revisar código de instrumentação
- Follow the skill skill-frontend-instrumentation-otel (checklist "revisão").
- Verify: names centralized in
telemetry/names.ts, semconv attributes, error counter without_totaland withoutmessagelabel, single SERVICE_NAME usage, documentation code → Grafana where relevant. - Report missing items with concrete suggestions (code snippet or file path).
References
- Skill:
.cursor/skills/frontend/skill-frontend-instrumentation-otel/SKILL.md - Rule:
.cursor/rules/frontend-instrumentation.md - Doc (no projeto):
telemetria/docs/frontend-opentelemetry.md(quando existir)
Remember: Read the skill file first, then follow its checklists. The skill contains instrumentation flows, mapeamento código → Grafana, and best practices.
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 · 45 lines · 47 tokens per session scan A 1dfbbf821cba
agt-dev-frontend-instrumentation is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 511 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-30.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.