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 camilooscargbaptista/cto-toolkit --skill team-scalinggit clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkitWrote 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/camilooscargbaptista/cto-toolkit/team-scaling)<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/team-scaling"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/team-scaling/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/camilooscargbaptista/cto-toolkit/team-scaling"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/team-scaling.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.00095 | $0.01543 |
| Opus 5 | $0.00048 | $0.00772 |
| Sonnet 5 | $0.00019 | $0.00309 |
| Haiku 4.5 | $0.00010 | $0.00154 |
Grade A, and why
team-scaling 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Scaling & Engineering Organization
You are a VP of Engineering who has scaled engineering orgs from 5 to 500+. You know that the org chart is the architecture — Conway's Law is real. You design teams that can ship independently.
Directive: Read ../quality-standard/SKILL.md before producing output.
Engineering Ladder
Individual Contributor Track
| Level | Title | Scope | Key Behaviors |
|---|---|---|---|
| IC1 | Junior Engineer | Task-level | Executes well-defined tasks, learns codebase, asks good questions |
| IC2 | Mid Engineer | Feature-level | Independently delivers features, writes tests, reviews PRs |
| IC3 | Senior Engineer | System-level | Designs systems, mentors juniors, drives technical decisions |
| IC4 | Staff Engineer | Org-level | Cross-team technical leadership, architecture, tech strategy |
| IC5 | Principal Engineer | Company-level | Sets technical direction, solves hardest problems, industry influence |
Management Track
| Level | Title | Scope | Key Behaviors |
|---|---|---|---|
| M1 | Engineering Manager | Team (5-8 ICs) | Hiring, 1:1s, delivery, people development |
| M2 | Senior EM | Multiple teams | Process improvement, cross-team coordination |
| M3 | Director | Department | Strategy, budget, org design, senior hiring |
| M4 | VP Engineering | All engineering | Vision, culture, executive alignment, scaling |
Promotion Criteria
- Already operating at next level for 3-6 months (not a promise of future performance)
- Impact documented with specific examples
- Peer feedback supports the case
- Manager + skip-level alignment
- No "tenure-based" promotions (time ≠ growth)
Team Topologies
Team Types (based on Team Topologies by Skelton & Pais)
| Type | Purpose | Size | Examples |
|---|---|---|---|
| Stream-aligned | Delivers value in a specific domain | 5-9 | Checkout team, Onboarding team |
| Platform | Provides self-service capabilities | 4-8 | Infrastructure, CI/CD, Developer portal |
| Enabling | Helps stream-aligned teams adopt new skills | 2-4 | Security specialists, ML enablement |
| Complicated subsystem | Owns technically complex components | 3-6 | Payment processing, Search engine |
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 · 181 lines · 95 tokens per session scan A 570fbd139a54
team-scaling is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session and 1,543 once invoked, about $0.0005 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
hackman-enabling-conditions
Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance…
leadership-pipeline
Diagnoses leadership development blockages using Charan's six passage transitions from individual contributor through enterprise manager. Evaluates skills, time allocation, and values shifts required at each leadership level. Use when founders cannot let go of operational tasks, managers are failing after promotion…
apply-peter-principle-check
Use when designing a promotion process or deciding whether to promote someone based on strong current-role performance — explicitly test whether the skills that made them successful there are the same skills the next level requires, because promotion systems that reward current-role performance alone systematically…
A Player定义（A类人才识别标准）
A guide for defining and identifying A Players: full-time employees who rank among the top part of the available talent pool and are willing to accept the job offer.
head-of-sales
VP Sales advisor for founders and first-time sales managers building and scaling sales teams.
workspace-manager
Registers, lists, removes, and assigns workspaces (project directories) for Anima work. Use when: binding project paths to Anima, managing aliases, or switching workspace roots.