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 nps-proxygit 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/nps-proxy)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/nps-proxy"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/nps-proxy/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/nps-proxy"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/nps-proxy.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.00047 | $0.01541 |
| Opus 5 | $0.00023 | $0.00771 |
| Sonnet 5 | $0.00009 | $0.00308 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade A, and why
nps-proxy 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.
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.
NPS Proxy
Measure user satisfaction from behavior when you don't have survey data — frustration signals, engagement patterns, and conversion behavior as a real-time proxy for how users feel.
When to Use
- "What's our user satisfaction looking like?"
- "We don't run NPS surveys — can Fullstory give us a satisfaction signal?"
- "Which users are likely promoters vs detractors based on behavior?"
- "Did satisfaction improve after the redesign?"
- "Show me our 'frustration score' trend over time"
Mental Model
NPS (Net Promoter Score) asks users: "How likely are you to recommend us?" Fullstory doesn't do surveys. But you can build a behavioral proxy from three signals:
- Success signals (promoters): Completed key tasks, returned multiple times, used advanced features, high engagement
- Frustration signals (detractors): Rage clicks, dead clicks, errors, form abandonment, one-and-done sessions
- Engagement signals (passives): Consistent but shallow usage, moderate session frequency, no strong positive or negative signals
The ratio of success to frustration signals gives you a directional satisfaction measure. It's not a survey. It's a behavioral proxy. Treat it accordingly.
Workflow
Step 1: Define success and frustration signals
Work with the user to define what "happy" and "unhappy" look like in their product:
Success signals (any 2+ = likely satisfied):
- Completed a purchase, signup, or key conversion
- Used the product 3+ times in 30 days
- Session duration >5 minutes (engaged, not bouncing)
- Used advanced features (beyond basics)
- Returned after first session (retained)
- No frustration events in any session
Frustration signals (any 1 = likely unsatisfied):
- Rage clicked any element
- Dead clicked any element
- Hit a console error or network failure
- Abandoned a form mid-completion
- Bounced after 1 page view (<10 seconds)
- Visited help/support pages repeatedly
Step 2: Build satisfaction segments
fullstory:build_segment("users with at least 2 success signals and 0 frustration signals in last 30 days") → promoters
fullstory:build_segment("users with at least 1 frustration signal in last 30 days") → detractors
fullstory:build_segment("users with neither strong success nor frustration signals in last 30 days") → passives
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 · 149 lines · 47 tokens per session scan A 6d1f17ca0df0
nps-proxy is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 27d ago), licensed MIT. It adds 47 tokens to every session and 1,541 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-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.