metrics-and-events-planner

metrics-and-events-planner is a skill for Claude Code, Codex from staruhub/CrewClaw. It costs 22 tokens per session (208 once invoked), scanned A, original, Apache-2.0.

A guide for defining product success measures and the named events that record user actions for analysis.

In plain words
What is it for?
Use it to choose a primary metric, supporting signals, event names, useful properties, and risks in interpreting the results.
Why use it?
It connects measurement to product decisions while avoiding arbitrary benchmarks and collection of sensitive content such as code or private documents.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to choose a primary metric, supporting signals, event names, useful properties, and risks in interpreting the results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/staruhub/crewclaw/metrics-and-events-planner
Install

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.

Any agent
npx skills add staruhub/CrewClaw --skill metrics-and-events-planner
Clone the repo
git clone --depth 1 https://github.com/staruhub/CrewClaw

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for metrics-and-events-planner

README.md
[![agentmods](https://agentmods.dev/badge/skills/staruhub/crewclaw/metrics-and-events-planner/github.svg)](https://agentmods.dev/skills/staruhub/crewclaw/metrics-and-events-planner)
Your own site
<a href="https://agentmods.dev/skills/staruhub/crewclaw/metrics-and-events-planner"><img src="https://agentmods.dev/badge/skills/staruhub/crewclaw/metrics-and-events-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for metrics-and-events-planner

Your own site · 80×15
<a href="https://agentmods.dev/skills/staruhub/crewclaw/metrics-and-events-planner"><img src="https://agentmods.dev/badge/skills/staruhub/crewclaw/metrics-and-events-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00208
Opus 5 $0.00011 $0.00104
Sonnet 5 $0.00004 $0.00042
Haiku 4.5 $0.00002 $0.00021

Measured 12d ago against content hash 51f661935ca0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

metrics-and-events-planner 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 12d 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.

experts/product-prd-crab/skills/product/metrics-and-events-planner/SKILL.md · 38 lines

What it actually says

Metrics And Events Planner

Overview

Suggest simple metrics that connect product behavior to learning.

When to Use

Use when a PRD needs success metrics, activation signals, retention signals, or event instrumentation.

Workflow

  1. Identify the decision the metric should support.
  2. Define one primary metric and supporting signals.
  3. Suggest event names and key properties.
  4. Exclude sensitive user content.
  5. Name interpretation risks.

Common Pitfalls

  • Do not invent benchmarks.
  • Do not collect prompt, code, secrets, or private documents.
  • Do not add metrics that no one will use.

Verification Checklist

  • Metrics answer a decision question.
  • Events avoid sensitive payloads.
  • Interpretation risks are explicit.
Changes

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.

  1. 12d ago First seen · 38 lines · 22 tokens per session scan A 51f661935ca0

Subscribe to this mod's changes

metrics-and-events-planner is a skill published in the GitHub repository staruhub/CrewClaw (22 stars, last pushed 6d ago), licensed Apache-2.0. It adds 22 tokens to every session and 208 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-30.

Related

Other skills, from other repositories

agent-carnet

Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.

yamadashy/repomix · 67 tokens

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

security-audit

Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.

omnigent-ai/omnigent · 64 tokens

routing-card-authoring

Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.

agentlas-ai/Agentlas-OS · 68 tokens

taiyi-evolve

A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.

Dong90/oh-my-taiyiforge · 37 tokens

taiyi-diagram-c4

A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.

Dong90/oh-my-taiyiforge · 48 tokens