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 beingsmit/technical-product-gtm --skill operating-cadencegit clone --depth 1 https://github.com/beingsmit/technical-product-gtmWrote 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/beingsmit/technical-product-gtm/operating-cadence)<a href="https://agentmods.dev/skills/beingsmit/technical-product-gtm/operating-cadence"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/operating-cadence/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/beingsmit/technical-product-gtm/operating-cadence"><img src="https://agentmods.dev/badge/skills/beingsmit/technical-product-gtm/operating-cadence.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.00053 | $0.03738 |
| Opus 5 | $0.00026 | $0.01869 |
| Sonnet 5 | $0.00011 | $0.00748 |
| Haiku 4.5 | $0.00005 | $0.00374 |
Grade A, and why
operating-cadence 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.
This is a copy
95% identical to gtm-operating-cadence — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating Cadence
The meeting structure that worked at 30 people collapses at 100. What worked at 100 collapses at 300. The failure mode is always the same: too many people in too many meetings making too few decisions.
When to Use
Triggers:
- "Our meetings don't produce decisions"
- "We're growing but alignment is getting worse"
- "How often should we meet?"
- "Nobody knows what's happening across functions"
- "Decisions take forever"
- "Leadership is in meetings all day"
Context:
- Companies scaling from 20 to 300+ people
- Post-PMF through growth stage
- Distributed / remote teams
- Any stage where "we need to talk about this" has become the default
Core Frameworks
1. The Five-Level Meeting Architecture
The Pattern:
Different meetings serve different purposes. Conflating them creates either inefficiency (too much time) or confusion (unclear decisions). Separate meetings by function, frequency, and decision authority.
Level 1: Daily Standup (15 min, teams only)
- What we finished yesterday, what we're starting today, what's blocking us
- 5-10 people max. Whole-company standups are theater
- Anti-pattern: Status reporting (use Slack, not meetings)
- Anti-pattern: Strategic discussion (wrong time, wrong place)
- Success criteria: Finishes in 15 minutes, surfaces 1-2 blockers
Level 2: Weekly Functional Reviews (60 min, function leadership)
Each function gets its own weekly rhythm:
- Product team Friday 4pm: metrics, user feedback, roadmap blockers
- GTM team Tuesday 4pm: pipeline, customer updates, deal health
- Engineering Wednesday 4pm: velocity, bug backlog, deployment
Format: Metric recap (10 min) → Wins/blockers (15 min) → One deep-dive (30 min) → Next week priorities (5 min)
Anti-pattern: Trying to solve every problem in the meeting. Pick 1-2, delegate the rest to follow-ups.
Level 3: Weekly All-Hands (60 min, whole company)
The single most important alignment mechanism at a scaling company.
- CEO update (15 min): north star progress, week focus, what's changed
- Metric dashboard (10 min): same format every week (consistency enables pattern recognition)
- Deep dive (20 min): one strategic topic needing team input — not a presentation, a discussion
- Q&A (15 min): real questions, real answers
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 · 422 lines · 53 tokens per session scan A ccd6036538a0
operating-cadence is a skill published in the GitHub repository beingsmit/technical-product-gtm (42 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 3,738 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to gtm-operating-cadence, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
seo-strategy
Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
support-operations
Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…