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 varunk130/ai-gtm-skill-library --skill flywheel-syncgit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/varunk130/ai-gtm-skill-library/flywheel-sync)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/flywheel-sync"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/flywheel-sync/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/varunk130/ai-gtm-skill-library/flywheel-sync"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/flywheel-sync.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.00055 | $0.03495 |
| Opus 5 | $0.00028 | $0.01747 |
| Sonnet 5 | $0.00011 | $0.00699 |
| Haiku 4.5 | $0.00006 | $0.00349 |
Grade A, and why
flywheel-sync 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 10d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flywheel Sync (ORBIT System)
A meta-skill that operates above all other skills in the launch engine, auditing the health of skill-to-skill connections, identifying broken handoffs, redundant outputs, and bottlenecks, then generating a continuous improvement roadmap. ORBIT ensures the entire product launch system functions as an integrated flywheel rather than a collection of disconnected processes.
When to Use
- Auditing whether the launch engine skills are working together effectively
- Diagnosing why a launch process feels slow, disconnected, or redundant
- Identifying gaps where important outputs are missing or not being consumed
- Checking if skill cadences are aligned with business rhythms
- Building a continuous improvement roadmap for the overall launch system
- Onboarding new team members to understand how skills interconnect
- Preparing for a major launch by verifying all system connections are healthy
What You'll Need
Critical inputs (ask if not provided):
- List of active skills and their current usage status
- Recent outputs from each skill (or confirmation that skills have been run)
- Known pain points or friction in the current launch process
- Team structure and ownership map across skills
- Launch cadence (how often launches occur, what types)
Nice-to-have:
- Outputs from the most recent run of each skill
- Timestamps of last skill execution
- Team feedback on handoff quality and timing
- Historical launch debriefs (from launch-debrief)
- Current launch calendar and upcoming milestones
Process
Step 1: Map the Full Skill Connection Graph
Document every skill-to-skill connection in the launch engine with its expected data flow.
Skill Connection Matrix:
| From Skill | To Skill | Output Passed | Format | Timing | Status |
|---|---|---|---|---|---|
| signal-radar | battle-scanner | Market signals, trend data | Report | Weekly to Monthly | |
| signal-radar | position-lock | Emerging trends, whitespace | Report | Weekly to Quarterly | |
| battle-scanner | position-lock | Competitive landscape, gaps | Framework | Monthly to Quarterly | |
| battle-scanner | enablement-forge | Competitive battle cards | Cards | Monthly to Per-launch | |
| position-lock | demand-engine | Messaging framework, value props | Framework | Quarterly to Per-launch | |
| position-lock | enablement-forge | Messaging hierarchy, proof points | Framework | Quarterly to Per-launch | |
| demand-engine | budget-allocator | WAVE scores, channel strategy | Scored list | Per-launch | |
| demand-engine | launch-command | Channel activation plan | Plan | Per-launch | |
| journey-architect | demand-engine | Touchpoint map, stage definitions | Map | Per-launch | |
| journey-architect | growth-loop | Post-purchase journey stages | Map | Per-launch | |
| enablement-forge | launch-command | Sales materials inventory | Checklist | Per-launch | |
| budget-allocator | launch-command | Spend allocation plan | Model | Per-launch | |
| launch-command | launch-pulse | Launch plan, workstream status | Dashboard | Per-launch | |
| launch-pulse | growth-loop | Adoption and retention metrics | Metrics | Continuous | |
| launch-pulse | launch-debrief | Actuals vs targets | Scorecard | T+30, T+90 | |
| growth-loop | demand-engine | Referral pipeline, case studies | Assets | Continuous | |
| growth-loop | signal-radar | Customer signals, advocacy data | Signals | Continuous | |
| launch-debrief | All skills | Updated benchmarks, learnings | Playbook | Post-launch | |
| flywheel-sync | All skills | Health report, improvement roadmap | Dashboard | Quarterly |
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.
- 10d ago First seen · 278 lines · 55 tokens per session scan A 995d543c3633
flywheel-sync is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 3,495 once invoked, about $0.0003 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
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…