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 content-funnel-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/content-funnel-design)<a href="https://agentmods.dev/skills/event4u-app/agent-config/content-funnel-design"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/content-funnel-design/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/event4u-app/agent-config/content-funnel-design"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/content-funnel-design.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.00043 | $0.01979 |
| Opus 5 | $0.00022 | $0.00989 |
| Sonnet 5 | $0.00009 | $0.00396 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
content-funnel-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 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
content-funnel-design
When to use
- A team has content but no funnel — each asset is shaped to its author's preference, not to the funnel stage the audience is in.
- The cadence (
editorial-calendar) is locked but one funnel stage is leaking and there is no content shape that would catch it. - A new ICP requires re-mapping content shapes per stage because the previous mapping was inherited from a previous segment.
Do NOT use to plan publishing cadence (route to editorial-calendar),
diagnose quantitative drop-off (route to funnel-analysis), or
draft the asset itself (downstream of this skill).
Cognition cluster
- Mental model 14 — Meadows leverage points. Some funnel stages
are parameters (small change, small ripple) and some are
structure (small change, system-wide ripple). The content
funnel design is the discipline of placing the heaviest content
investment at the structural leverage point, not the parameter
one. See
docs/contracts/mental-models.md§ 14. - Mental model 6 — Theory of constraints. The slow funnel stage
caps the whole pipeline. Adding content elsewhere does not loosen
the constraint. See
mental-models.md§ 6. - Mental model 16 — Leading vs. lagging indicators. Time-to-
proof (asset → activation question) is leading; pipeline lift is
lagging. The funnel design is gated on leading signals, not on
the lagging ones the board sees a quarter later. See
mental-models.md§ 16. - **Context-spine — funnel-stage + channel-stage + customer-segment
- product.** Read funnel-stage for which stage owns each
content shape, channel-stage for where the audience meets
the asset, customer-segment for whose questions the asset
answers, and product for the proofs the asset can actually
back. See
context-spine.
- product.** Read funnel-stage for which stage owns each
content shape, channel-stage for where the audience meets
the asset, customer-segment for whose questions the asset
answers, and product for the proofs the asset can actually
back. See
Procedure
Step 0: Inherit the funnel diagnosis
Identify the leaking stage from
funnel-analysis and the cadence
classification from editorial-calendar.
The content funnel design is a response to a diagnosed leak —
without the diagnosis, content investment is uniform and the
constraint stays where it is.
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 · 182 lines · 43 tokens per session scan A b69158749742
content-funnel-design is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,979 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.