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.5 | $0.00022 | $0.01398 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (7 stars, last pushed 10d ago), licensed MIT. It adds 55 tokens to every session and 3,495 once invoked, about $0.0002 per session on Opus 5.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
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
board-meeting
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /c-level-agents:boardroom, calls a…
wrap-up
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes…