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 baodq97/open-plugin --skill cto-playbookgit clone --depth 1 https://github.com/baodq97/open-pluginWrote 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/baodq97/open-plugin/cto-playbook)<a href="https://agentmods.dev/skills/baodq97/open-plugin/cto-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/cto-playbook/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/baodq97/open-plugin/cto-playbook"><img src="https://agentmods.dev/badge/skills/baodq97/open-plugin/cto-playbook.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.00161 | $0.01864 |
| Opus 5.5 | $0.00064 | $0.00746 |
| Sonnet 5.5 | $0.00032 | $0.00373 |
| Haiku 4.5 | $0.00016 | $0.00186 |
Grade A, and why
cto-playbook 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CTO Playbook v1.0
Guides engineering leads and VPs through Technology Leadership tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build CTO competency from SFIA level 5 (Ensure, advise) toward level 6-7.
Core Principles
- Hybrid guidance — Walk through CTO phases together, not just instruct. Recommend strategies, draft artifacts collaboratively, and help complete the task.
- SFIA-mapped coaching — Every activity maps to a SFIA skill and level. Inline coaching explains what skill is being practiced and how to level up.
- Flexible phases — 5 phases provide structure, but skip or jump as context demands. No forced quality gates.
- Artifacts over theory — Each phase produces concrete deliverables (technology vision, innovation strategy, governance frameworks), not just checklists.
- Innovation with purpose — Evaluate and adopt emerging technologies only when they advance the organisation's competitive position.
- CTO does not own the product roadmap — CTO provides technical vision and capability assessment, product priorities are set by the CPO/product team.
CTO Workflow — 5 Phases
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Assess technology landscape, market trends, competitive position | EMRG, ITSP, RLMT | Technology landscape assessment, Market/competitor analysis, Technical debt inventory, Engineering capability assessment |
| 2 | Envision | Define technology vision, innovation strategy, platform direction | STPL, ITSP, INOV, TECH | Technology vision document, Innovation strategy, Platform architecture principles, Build vs Buy analysis |
| 3 | Build | Establish engineering practices, development standards, team structure | DLMG, GOVN, OCDV | Engineering standards, Development practices guide, Team topology, Technology governance framework |
| 4 | Scale | Scale systems, processes, and teams | ITMG, DLMG, SUPP, FMIT | Scaling strategy, Performance benchmarks, Vendor/partner strategy, Technology budget |
| 5 | Evolve | Monitor emerging tech, adapt strategy, drive continuous innovation | EMRG, INOV, BURM, TECH | Technology radar, Innovation pipeline, Risk assessment, Strategy refresh document |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 184 lines · 161 tokens per session scan A 5fa713cc8ee3
cto-playbook is a skill published in the GitHub repository baodq97/open-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 161 tokens to every session and 1,864 once invoked, about $0.0006 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
metrics-dashboard
Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan.
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…
interview-script
Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.
ab-test-analysis
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.