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 event4u-app/agent-config --skill activation-designgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/activation-design)<a href="https://agentmods.dev/skills/event4u-app/agent-config/activation-design"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/activation-design.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.00039 | $0.01986 |
| Opus 5 | $0.00019 | $0.00993 |
| Sonnet 5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00199 |
Grade A, and why
activation-design 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
activation-design
When to use
- The activation event is "signed up" or "logged in" and the funnel looks healthy while retention sinks — the event does not correlate with paid or D30, so the metric is a vanity surface.
- A new segment is being routed against an activation event built for a previous segment — the aha moment differs by segment and the metric needs to be re-keyed.
- A product loop redesign needs activation to complete the loop's first cycle (handover from
retention-loops) — the activation event must match the binding loop's first reward, not an arbitrary product step.
Do NOT use to design the day-0-to-day-30 milestone path (route to
onboarding-design), the long-running retention loops themselves
(route to retention-loops), or the full visitor-to-paid funnel
diagnosis (route to funnel-analysis).
Cognition cluster
- Mental model 9 — Hypothesis-driven thinking. "Event E is the
activation moment because users who reach E retain at <rate>
vs <base>" is a falsifiable claim with evidence. "E feels
important" is not. Pick the event that survives the
hypothesis test. See
docs/contracts/mental-models.md§ 9. - Mental model 16 — Leading vs. lagging indicators. Paid is
lagging; the activation event must be leading — observable
before the user has paid, and correlated with the lagging
outcome. An activation event that is itself lagging cannot drive
a decision in time. See
mental-models.md§ 16. - Mental model 13 — Occam's razor. When candidate events
compete, the simpler one (single observable action) wins if it
correlates as well as a composite. Composite events hide
noise behind apparent precision. See
mental-models.md§ 13. - Context-spine — product + customer-segment + funnel-stage.
Read the product slot for what counts as a meaningful
buyer action in-product (the action must be observable in
instrumentation), the customer-segment slot for the
segment's switch-event (the aha moment is the segment's job
done once), and the funnel-stage slot for activation's
position relative to signup and paid. See
context-spine.
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 · 170 lines · 39 tokens per session scan A c8608c298f3a
activation-design is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,986 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-31.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.