agentmods.dev

initializing-vertical-flywheel

initializing-vertical-flywheel is a skill for Claude Code from jianzhichun/emerge. It costs 36 tokens per session (1,930 once invoked), scanned A, original, MIT.

A setup guide for turning a plain-language request into the files and checks needed to start a domain-specific workflow.

In plain words
What is it for?
Use it to initialize a new workflow area, create its assets, verify that it runs, and make its policy state visible. It follows TDD, meaning tests are written first, made to pass, and then cleaned up.
Why use it?
It helps when the request leaves out important environment details or mixes assumptions with actions. It also requires tests and working read/write checks before setup is called complete.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the emerge plugin — 15 skills, 10 commands, 3 agents, 24 hooks shipped together

not rated 107repo 4mo ago A scan 36 tokens original MIT

Good fit Use it to initialize a new workflow area, create its assets, verify that it runs, and make its policy state visible. It follows TDD, meaning tests are written first, made to pass, and then cleaned up.

Compare 6 skills from other repositories ↓
View source ↗ jianzhichun/emerge
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add jianzhichun/emerge
Claude Code
/plugin install emerge

Made for: Claude Code.

Or install emerge, the plugin that ships this one along with the rest of its 15 skills, 10 commands, 3 agents, 24 hooks.

Wrote 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.

agentmods badge for initializing-vertical-flywheel

README.md
[![agentmods](https://agentmods.dev/badge/skills/jianzhichun/emerge/initializing-vertical-flywheel/github.svg)](https://agentmods.dev/skills/jianzhichun/emerge/initializing-vertical-flywheel)
Your own site
<a href="https://agentmods.dev/skills/jianzhichun/emerge/initializing-vertical-flywheel"><img src="https://agentmods.dev/badge/skills/jianzhichun/emerge/initializing-vertical-flywheel/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.

agentmods 80×15 button for initializing-vertical-flywheel

Your own site · 80×15
<a href="https://agentmods.dev/skills/jianzhichun/emerge/initializing-vertical-flywheel"><img src="https://agentmods.dev/badge/skills/jianzhichun/emerge/initializing-vertical-flywheel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,930 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01930
Opus 5 $0.00018 $0.00965
Sonnet 5 $0.00007 $0.00386
Haiku 4.5 $0.00004 $0.00193

Measured 9d ago against content hash 6c8b41632ae0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

initializing-vertical-flywheel 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.

skills/initializing-vertical-flywheel/SKILL.md · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Initializing Vertical Flywheel

Overview

Use this skill to convert one natural-language bootstrap request into concrete vertical flywheel assets under ~/.emerge/connectors/<vertical>/, plus verified runtime readiness. Never place vertical connectors inside the plugin project directory.

Core principle: do not claim initialization complete until new read/write pipelines execute and policy state is observable.

When to Use

  • User asks for one-sentence bootstrap, such as "initialize desktop_drafting_app vertical flywheel".
  • User context is natural language, not strict parameters.
  • Environment assumptions are uncertain (host/tooling/executor not guaranteed).

Do not use when:

  • User only asks for explanation, not initialization.
  • User asks only for policy status or read-only review.

Mandatory TDD Flow

  1. RED: add/init tests for the requested vertical and watch them fail.
  2. GREEN: add minimum assets and code to make tests pass.
  3. REFACTOR: harden naming, verification, and output shape without changing behavior.

No bootstrap completion claim without RED and GREEN evidence.

Core Initialization Contract

  • Input is user natural language; do not force CLI-style parameter declarations.
  • Extract only what is explicit in user text.
  • Ask only minimal clarifying questions when execution cannot proceed.
  • Produce:
    • bootstrap status (init_ok, degraded, or blocked)
    • created/updated assets
    • next verification actions

Remote runner setup (when needed)

If the user context indicates remote execution, initialize runner connectivity first.

Minimum steps:

  1. Generate install URLs from local plugin root (or Cockpit Monitors → Add Runner):
    • python3 "${CLAUDE_PLUGIN_ROOT}/scripts/repl_admin.py" runner-install-url --target-profile "<target_profile>" --pretty
  2. Send the printed command to the operator; they run it on the target machine (self-install).
  3. Verify with one icc_exec smoke call before creating vertical assets.
  4. Verify admin health signal:
    • python3 "${CLAUDE_PLUGIN_ROOT}/scripts/repl_admin.py" runner-status --pretty
    • proceed only when Runner reachable: True.

Read the full file on GitHub · 205 lines

Changes

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.

  1. 9d ago First seen · 205 lines · 36 tokens per session scan A 6c8b41632ae0

Subscribe to this mod's changes

initializing-vertical-flywheel is a skill published in the GitHub repository jianzhichun/emerge (107 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,930 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-30.

Planning
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens