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 ariadoss/superskills --skill hooked-uxgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/hooked-ux)<a href="https://agentmods.dev/skills/ariadoss/superskills/hooked-ux"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/hooked-ux/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/ariadoss/superskills/hooked-ux"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/hooked-ux.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.00122 | $0.03314 |
| Opus 5 | $0.00061 | $0.01657 |
| Sonnet 5 | $0.00024 | $0.00663 |
| Haiku 4.5 | $0.00012 | $0.00331 |
Grade A, and why
hooked-ux 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hooked — 88% identical, 51 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Model Framework
Framework for building habit-forming products. Based on a fundamental truth: habits are not created—they are built through successive cycles through the Hook.
Core Principle
The Hook Model = a four-phase process that connects the user's problem to your solution frequently enough to form a habit.
Trigger → Action → Variable Reward → Investment
↑ │
└──────────────────────────────────────┘
Habit Zone: Products enter the "habit zone" when used frequently enough and with enough perceived value. The goal is to move users from deliberate usage to automatic, habitual behavior.
Scoring
Goal: 10/10. When reviewing or creating product engagement mechanics, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
The Four Phases
1. Trigger
Core concept: The actuator of behavior. What prompts the user to take action? Triggers come in two forms: external (environment-driven) and internal (emotion-driven). The ultimate goal is to move users from external triggers to internal triggers.
Why it works: Every habit starts with a cue. Without a trigger, there is no behavior. External triggers get users started, but internal triggers — emotions like boredom, loneliness, uncertainty, or fear of missing out — are what drive unprompted, habitual usage. When your product becomes the automatic response to an internal trigger, you have a habit.
Key insights:
- External triggers (push notifications, emails, buttons, ads, word of mouth) initiate behavior early on
- Internal triggers (emotions, routines, situations) are the ultimate goal — users prompt themselves
- The goal is to move users from external triggers to internal triggers over time
- Map your product to the specific negative emotion it resolves (boredom, loneliness, confusion, FOMO)
- Effective external triggers must be well-timed, actionable, and lead to the simplest possible next action
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 · 268 lines · 122 tokens per session scan A df01d554201b
hooked-ux is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 3,314 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…