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 fernando-bertholdo/4-successful-AI-life --skill hookedgit clone --depth 1 https://github.com/fernando-bertholdo/4-successful-AI-lifeWrote 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/fernando-bertholdo/4-successful-ai-life/hooked)<a href="https://agentmods.dev/skills/fernando-bertholdo/4-successful-ai-life/hooked"><img src="https://agentmods.dev/badge/skills/fernando-bertholdo/4-successful-ai-life/hooked/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/fernando-bertholdo/4-successful-ai-life/hooked"><img src="https://agentmods.dev/badge/skills/fernando-bertholdo/4-successful-ai-life/hooked.svg" alt="Reviewed on agentmods" width="80" 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.00120 | $0.04063 |
| Opus 5.5 | $0.00048 | $0.01625 |
| Sonnet 5.5 | $0.00024 | $0.00813 |
| Haiku 4.5 | $0.00012 | $0.00406 |
Grade A, and why
hooked 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 1mo 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.
This is a copy
88% identical to hooked-ux — 51 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 313 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 ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 313 lines · 120 tokens per session scan A d9faecc40260
hooked is a skill published in the GitHub repository fernando-bertholdo/4-successful-AI-life (2 stars, last pushed 10d ago), licensed MIT. It adds 120 tokens to every session and 4,063 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to hooked-ux, differing in 51 lines, and is treated as a copy.
Other skills, from other repositories
example-feature-generator
Generate boilerplate for new features following project conventions. Use when user says "create feature", "add feature", or "new feature scaffolding".
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
agent-flutter-developer
Specialist subagent: Flutter/Dart cross-platform development, Riverpod state management, and platform channels specialist. Use when building Flutter apps, implementing state management, or working with native platform features. Trigger phrases: Flutter, Dart, Riverpod, Bloc, widget, MaterialApp, GoRouter, platform…
content-repurposer
Adapt content across platforms with tone/format shifting — blog to social, long to short, text to visual outline. Use when repurposing content for different channels, audiences, or formats.
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.