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 feature-adoptiongit 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/feature-adoption)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/feature-adoption"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/feature-adoption/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/feature-adoption"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/feature-adoption.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.00045 | $0.01315 |
| Opus 5 | $0.00023 | $0.00658 |
| Sonnet 5 | $0.00009 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
feature-adoption 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Adoption
Track how users adopt new features — who's using it, how deeply, are they coming back, and what's preventing adoption.
When to Use
- "How many users have tried the new dashboard?"
- "Are users who tried the new search feature coming back to it?"
- "What's blocking adoption of the new onboarding flow?"
- "Compare feature usage between enterprise and free users"
- "Is the new feature replacing the old one, or are users using both?"
- "Show me sessions where users started using the new feature but stopped"
Mental Model
Feature adoption is a funnel:
- Awareness: Users who saw the feature (visited the page, saw the announcement)
- Trial: Users who tried it (clicked on it, interacted once)
- Adoption: Users who used it repeatedly (came back, integrated into workflow)
- Retention: Users who are still using it N days later
The drop-off between each stage tells you where the problem is.
Workflow
Step 1: Define the feature
Clarify what "using the feature" means:
- A page visit? (e.g., visited /dashboard/new)
- A click event? (e.g., clicked "New Report" button)
- A custom event? (e.g.,
feature_search_v2_used) - A sequence? (e.g., visited /search → typed query → clicked result)
Step 2: Measure awareness
How many users encountered the feature?
fullstory:build_metric(
query="users who visited /dashboard/new",
output_type="single_number"
)
If this number is low, the problem is discovery, not the feature itself.
Step 3: Measure trial
Of those who were aware, how many tried it?
fullstory:build_metric(
query="users who interacted with the new dashboard (clicked any element or spent >10 seconds)",
output_type="single_number"
)
Trial rate = trial users / aware users. Low trial rate = the feature doesn't look compelling or its purpose isn't clear.
Step 4: Measure adoption (repeat usage)
Of those who tried it, how many came back?
fullstory:build_segment("users who used new dashboard at least once")
fullstory:build_metric(query="sessions with new dashboard usage per user in last 30 days", output_type="top_n")
→ "60% used it once, 25% used it 2-3 times, 15% used it 4+ times"
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.
- 11d ago First seen · 149 lines · 45 tokens per session scan A 78f838d0bf1e
feature-adoption is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 45 tokens to every session and 1,315 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 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-networking
Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.
roblox-ui-design
Use for Roblox UI composition, hierarchy, visual systems, style inheritance, accessibility, and design review.