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 pmprompt/claude-plugin-product-management --skill hooked-modelgit clone --depth 1 https://github.com/pmprompt/claude-plugin-product-managementWrote 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/pmprompt/claude-plugin-product-management/hooked-model)<a href="https://agentmods.dev/skills/pmprompt/claude-plugin-product-management/hooked-model"><img src="https://agentmods.dev/badge/skills/pmprompt/claude-plugin-product-management/hooked-model.svg" alt="Measured on agentmods" 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.00076 | $0.00537 |
| Opus 5 | $0.00038 | $0.00269 |
| Sonnet 5 | $0.00015 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
hooked-model 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 8d 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-model — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
The Hooked Model
What It Is
The Hooked Model is a framework for building products that create unprompted user engagement. The core insight: habit-forming products connect to internal triggers through a repeating cycle of trigger, action, reward, and investment.
When a product becomes a habit, users engage without external prompts. They don't need ads, emails, or notifications to come back. They return because the product has become their automatic response to an internal trigger like boredom, loneliness, uncertainty, or FOMO.
The key shift: Move from asking "How do we get users to open the app?" to asking "What internal trigger do we want to own, and how do we become the automatic response to it?"
When to Use It
Use the Hooked Model when you need to:
- Design features that drive repeat engagement (not just one-time use)
- Reduce dependency on external marketing to bring users back
- Improve retention and decrease churn through habit formation
- Understand why competitor products are so sticky (reverse-engineer their hooks)
- Create ethical engagement that genuinely improves users' lives
- Prioritize which features to build based on habit potential
- Increase customer lifetime value through deeper product integration
When Not to Use It
- The product is inherently infrequent (e.g., buying a house, annual insurance)
- Users should consciously evaluate each decision (e.g., financial trading, medical diagnosis)
- Habit formation would harm users rather than help them
Resources
Books:
- Hooked: How to Build Habit-Forming Products by Nir Eyal
- Indistractable: How to Control Your Attention and Choose Your Life by Nir Eyal
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.
- 8d ago First seen · 55 lines · 76 tokens per session scan A 7cc3c9fe5f79
hooked-model is a skill published in the GitHub repository pmprompt/claude-plugin-product-management (48 stars, last pushed 6mo ago), licensed MIT. It adds 76 tokens to every session and 537 once invoked, about $0.0004 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
tool-design-sprint-readiness
Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, customer recruiting plan, and pre-sprint activities. Use when a team is considering…
tool-design-sprint-brief
Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Produces a two-page artifact the team and…
tool-design-sprint-decide-and-storyboard
Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives Thursday's prototype build. The most decision-heavy day of the sprint. Use Wednesday morning and afternoon after Tuesday's…
tool-design-sprint-map-and-target
Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morning and afternoon…
tool-design-sprint-prototype-plan
Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype brief (what to build, fidelity bar, time allocation per role), canonical Five-Act Interview script (Welcome, Context, Intro…
tool-design-sprint-sketch
Day 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author the sketches themselves. Use Tuesday…