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/vivekchand/clawmetry/clawmetrynpx skills add vivekchand/clawmetry --skill clawmetrygit clone --depth 1 https://github.com/vivekchand/clawmetryWhat 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.00051 | $0.00927 |
| Opus 5 | $0.00026 | $0.00464 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
clawmetry 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClawMetry Observability
You have access to ClawMetry — a full observability platform for OpenClaw agents. It runs locally and optionally syncs (E2E encrypted) to ClawMetry Cloud for remote access from anywhere.
Local Dashboard
The ClawMetry dashboard runs at http://localhost:8900 and provides:
- Overview — active sessions, total costs, token usage, system health
- Sessions — per-session token/cost breakdown, transcript viewer
- Brain — live feed of every LLM call with model, tokens, and latency
- Flow — animated architecture diagram showing real-time tool calls
- Memory — workspace memory file viewer (MEMORY.md, SOUL.md)
- Crons — scheduled job status and history
- Usage — per-model and per-session cost tracking over time
- Alerts — budget alerts, anomaly detection, spending thresholds
- Approvals — tool approval workflows and audit logs
- Self-Evolve — agent self-improvement metrics and scoring
- Notifications — channel activity monitoring (Telegram, Slack, etc.)
ClawMetry Cloud
When cloud sync is enabled (clawmetry connect), all telemetry is AES-256-GCM encrypted before leaving the machine and synced to clawmetry.com. This enables:
- Remote access — monitor your agents from any device, anywhere
- Multi-node fleet view — single dashboard for agents across multiple machines
- Persistent history — telemetry survives machine restarts and disk cleanups
- Team sharing — share observability with collaborators (coming soon)
The encryption key never leaves your machine. ClawMetry Cloud cannot read your data.
Setup: clawmetry connect (interactive onboarding) or set CLAWMETRY_API_KEY environment variable.
Data collected
ClawMetry observes diagnostic events from the OpenClaw runtime:
- Model usage — provider, model, input/output/cache tokens, cost, latency per LLM call
- Session lifecycle — start, end, state changes, stuck detection
- Tool calls — tool name, parameters, results, duration, errors
- Gateway logs — structured log forwarding for debugging
- Message flow — inbound/outbound message tracking across channels
- System health — heartbeats, uptime, active session counts
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.
- yesterday First seen · 85 lines · 51 tokens per session scan A 468b9c10f758
clawmetry is a skill published in the GitHub repository vivekchand/clawmetry (401 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 927 once invoked, about $0.0003 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 skills, from other repositories
go-rig
Use this skill when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary discipline, and structured code review. Complements CLAUDE.md by focusing on process and design judgment rather than version-specific Go…
frontend-dashboard
Use this skill when editing the embedded dashboard frontend in this repository. It focuses on preserving the single-file embedded SPA model, keeping the UI lightweight, and avoiding unnecessary frontend tooling or dependencies.
go-review
Use this skill when the task is to review Go code in this repository. Focus on bugs, regressions, API compatibility, test gaps, concurrency risks, and violations of the zero-dependency and root-facade constraints.
project-ops
Use this skill when working on repository operations in this project, including build, test, lint, release, CI alignment, Makefile-driven checks, and operational packaging constraints.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…