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 reatlat/fullstory-claude-plugin --skill quick-statsgit clone --depth 1 https://github.com/reatlat/fullstory-claude-pluginWrote 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/reatlat/fullstory-claude-plugin/quick-stats)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/quick-stats"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/quick-stats/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/reatlat/fullstory-claude-plugin/quick-stats"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/quick-stats.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.00437 |
| Opus 5 | $0.00026 | $0.00218 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
quick-stats 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 9d 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
Quick Stats
One-number answers. No analysis, no session investigation, no validation dance. Just the number, with context.
When to Use
- "How many users yesterday?"
- "What's the conversion rate this week?"
- "How many sessions today?"
- "How many rage clicks last month?"
- "What's our error count for this week?"
Short questions that expect a single numeric answer.
Workflow
Everything is one step: build, compute, present.
fullstory:build_metric(query="page views yesterday", output_type="single_number")
fullstory:compute_metric(metric_id)
Present: "12,340 page views yesterday (Aug 3)."
Add minimal context: "That's +3% vs the daily average last week" — but only if you already have the comparison data. Don't make extra calls to get it.
When NOT to Use
Don't use this skill if the question is:
- A comparison ("mobile vs desktop") →
comparisons - A trend ("is it getting worse?") →
general-analysis(trend metric) - A breakdown ("by page" or "by device") →
general-analysis(top_n metric) - A "why" question → any of the deep-dive skills
Quick Stats is for "what's the number" — nothing more.
Guidelines
- One metric, one compute call, one answer. No extra API calls.
- Include the time period in the answer: "12,340 page views yesterday" not "12,340 page views."
- Surface the
metric_urlso the user can verify. - If the metric already exists from a previous call in the conversation, reuse it. Don't rebuild.
- If the question needs validation (result is zero, looks wrong), don't use Quick Stats — upgrade to
general-analysiswhich handles validation.
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.
- 9d ago First seen · 50 lines · 52 tokens per session scan A 4856f61cc86f
quick-stats is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 27d ago), licensed MIT. It adds 52 tokens to every session and 437 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
roblox-input
Use when handling Roblox keyboard, mouse, gamepad, touch, motion input, or cross-platform action binding.
roblox-lighting
Use for Roblox lighting, atmosphere, day/night, or post-processing effects.
roblox-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.
roblox-growth-design
Use for growth diagnosis, discovery, retention, onboarding, experiments, LiveOps, and packaging.
roblox-data
Use when implementing player data persistence with DataStore, session ownership, schemas, migrations, or save and load flows.
roblox-networking
Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.