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 agentmods add skills/alebgl77/claude-inc/hook-generatornpx skills add alebgl77/claude-inc --skill hook-generatorgit clone --depth 1 https://github.com/alebgl77/claude-incWrote 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/alebgl77/claude-inc/hook-generator)<a href="https://agentmods.dev/skills/alebgl77/claude-inc/hook-generator"><img src="https://agentmods.dev/badge/skills/alebgl77/claude-inc/hook-generator.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 | $0.00102 | $0.00875 |
| Opus 5 | $0.00051 | $0.00438 |
| Sonnet 5 | $0.00020 | $0.00175 |
| Haiku 4.5 | $0.00010 | $0.00088 |
Grade A, and why
hook-generator 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Generator — Hook Smith
"Scroll-stopping hooks"
When to use
- "Give me hooks for a post about ."
- A finished draft with a flat first line: "punch up this opener."
- Titles and opening lines for a video or Reel, before scripting starts.
- "My content is good but nobody stops scrolling" — retrofit hooks onto existing work.
Workflow
- Ingest the content or topic and list what is genuinely surprising, valuable, or costly in it. A hook may only promise what this step actually finds.
- Note the audience and platform. LinkedIn hooks must survive a 2–3 line fold; X hooks ARE the post; video hooks must be speakable in two seconds.
- Generate 20 hooks covering all eight patterns, at least two per pattern: curiosity gap, contrarian, specific number, mistake/warning, transformation, insider secret, question, call-out-the-reader.
- Tag every hook with [pattern] and [platform fit: LI / X / video / all].
- Cash-check every hook against the content: does the material close this loop, back this claim, justify this number? Kill or rewrite anything that overdraws.
- Rank and pick the top three, each with a one-line rationale naming the audience, the promise, and the platform it fits.
- For the #1 pick, write the follow-through — the one or two lines that come immediately after the hook, so the earned attention isn't wasted.
Output format
## Hooks: <topic>
Audience: <who> | Platform: <where> | Source: <content analysed>
| # | Hook | Pattern | Fits |
|----|------|---------|------|
| 1 | <hook> | curiosity gap | LI / X |
| 2 | <hook> | contrarian | all |
| … | <20 rows total — all 8 patterns, 2+ each> | | |
### Top 3
1. "<hook>" — <pattern> — <why it wins for this audience on this platform>
2. "<hook>" — <pattern> — <rationale>
3. "<hook>" — <pattern> — <rationale>
### Follow-through for #1
<the next 1–2 lines after the hook>
### Killed in cash-check
<n> hooks — e.g. "<hook>" (promised <X>; the content only supports <Y>)
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.
- 4d ago First seen · 78 lines · 102 tokens per session scan A f827129db63c
hook-generator is a skill published in the GitHub repository alebgl77/claude-inc (14 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 875 once invoked, about $0.0005 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
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…