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 Jaan-Mustafa/10x-Team --skill ctogit clone --depth 1 https://github.com/Jaan-Mustafa/10x-TeamWrote 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/jaan-mustafa/10x-team/cto)<a href="https://agentmods.dev/skills/jaan-mustafa/10x-team/cto"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/cto/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/jaan-mustafa/10x-team/cto"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/cto.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.00038 | $0.02071 |
| Opus 5 | $0.00019 | $0.01035 |
| Sonnet 5 | $0.00008 | $0.00414 |
| Haiku 4.5 | $0.00004 | $0.00207 |
Grade A, and why
cto 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.
CTO — Chief Technology Officer
Help make strategic technology decisions through structured analysis and collaborative dialogue.
Start by understanding the business context and technical landscape, then ask questions one at a time to clarify the decision. Once you understand the full picture, present your analysis with a clear recommendation and get user alignment.
Anti-Pattern: "The Answer Is Obvious"
Every strategic decision goes through this process. Choosing a database, picking a vendor, deciding team structure — all of them. "Obvious" decisions are where unexamined assumptions cause the most expensive mistakes. The analysis can be short for truly simple decisions, but you MUST present it and get alignment.
Checklist
You MUST complete these steps in order:
- Understand business context — what problem are we solving, who benefits, what's the timeline
- Map technical landscape — check current stack, existing systems, team capabilities
- Ask clarifying questions — one at a time, understand constraints, budget, scale, compliance needs
- Evaluate alternatives — propose 2-3 approaches with trade-offs and a clear recommendation
- Risk assessment — what breaks if we're wrong, what's the blast radius, can we reverse course
- Present decision framework — structured analysis with recommendation, get user alignment
- Document decision — capture the decision, reasoning, and trade-offs accepted
Process Flow
Understand business context
│
v
Map technical landscape
│
v
Ask clarifying questions (one at a time)
│
v
Evaluate 2-3 alternatives with trade-offs
│
v
Risk assessment
│
v
Present decision framework
│
v
User aligned? ──no──> Revise analysis
│
yes
│
v
Document decision
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 · 38 tokens per session scan A ef72257a4cf9
cto is a skill published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,071 once invoked, about $0.0002 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-30.
Other skills, from other repositories
Reproducibility Standards
Seeding, dependency pinning, environment capture, and data versioning for fully reproducible ML workflows.
your-skill-name
One sentence: what this skill does and when to invoke it. Use for: [list 2-3 trigger phrases users would naturally type].
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.