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 skills add tomzx/agents --skill spec-analyticsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/skills/tomzx/agents/spec-analytics)<a href="https://agentmods.dev/skills/tomzx/agents/spec-analytics"><img src="https://agentmods.dev/badge/skills/tomzx/agents/spec-analytics/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.
<a href="https://agentmods.dev/skills/tomzx/agents/spec-analytics"><img src="https://agentmods.dev/badge/skills/tomzx/agents/spec-analytics.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00484 |
| Opus 5.5 | $0.00014 | $0.00194 |
| Sonnet 5.5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
spec-analytics 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 22d 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
Spec Analytics
Defines how an initiative will be measured at runtime. It is guardrail-first: it specifies the guardrail metrics (what must not regress) alongside the success metrics, because the classic failure is moving the metric you measured while breaking three you did not. This artifact is the PDLC counterpart to SDLC's telemetry plan; it can feed SDLC instrumentation.
Prerequisites
- Apply the shared PDLC conventions in
skills/pdlc/references/shared.md. acceptance-contract.mdandgoals.md(theSM-NandGM-Ndefinitions).
Steps
- List the analytics events required to compute every success metric (
SM-N) and guardrail metric (GM-N) fromgoals.md. Each event has a name, trigger, and payload. - Define the conversion funnels that show where value is created or lost.
- Define the dashboards: one per objective, showing success and guardrail metrics together so regressions are visible next to gains.
- For each guardrail, define the alert threshold and the response (who is paged, what is the rollback).
- Define the measurement windows: the early-window launch signals (from
launch-plan.md) and the steady-state cadence. - Flag metrics whose measurement source is not yet instrumented; route these to SDLC as instrumentation work.
- Write
analytics-spec.mdto the initiative directory.
Output Format
Use the template at skills/pdlc/templates/initiatives/analytics-spec.md.
Reference SM-N / GM-N IDs from goals.md.
Outcome
If $OUTCOME_YAML is set, emit verdict: drafted.
Completion Checklist
- Every
SM-NandGM-Nhas a defined event source - Guardrails have alert thresholds and a response owner
- Dashboards pair success and guardrail metrics
- Uninstrumented metrics flagged for SDLC
Next Step
After launch, load review-metrics to read the actuals.
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.
- 22d ago Changed · +4 lines 2711f01df6a1
- 24d ago Changed 30f3d8c45f43
- 1mo ago First seen · 44 lines · 35 tokens per session scan A 06550776d6fd
spec-analytics is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.