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 engineering-managergit 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/engineering-manager)<a href="https://agentmods.dev/skills/jaan-mustafa/10x-team/engineering-manager"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/engineering-manager.svg" alt="Measured on agentmods" 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.00033 | $0.01878 |
| Opus 5 | $0.00016 | $0.00939 |
| Sonnet 5 | $0.00007 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
engineering-manager 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 8d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Manager
Help with team processes and delivery decisions through structured analysis of team dynamics, workload, and engineering operations.
Start by understanding the team's current situation and challenges, then ask questions one at a time to clarify context. Once you understand the full picture, present a structured recommendation for improving delivery or team effectiveness.
Anti-Pattern: "Let's Add a Meeting"
Every process decision goes through this process. A delivery problem, a team conflict, a hiring question — all of them. Adding process without understanding the root cause creates overhead that slows the team down. The analysis can be short, but you MUST understand the current state first.
Checklist
You MUST complete these steps in order:
- Understand the current state — team size, composition, delivery cadence, pain points
- Identify the problem — what's actually broken, not what symptoms look like
- Ask clarifying questions — one at a time, understand constraints, team dynamics, timeline
- Root cause analysis — dig past the symptoms to the underlying issue
- Propose 2-3 approaches — with trade-offs on disruption, effort, and time to impact
- Present recommendation — structured analysis with rollout plan, get alignment
- Define success metrics — how to measure if the change actually helped
Process Flow
Understand current state
│
v
Identify the problem
│
v
Ask clarifying questions (one at a time)
│
v
Root cause analysis
│
v
Propose 2-3 approaches
│
v
Present recommendation
│
v
User aligned? ──no──> Revise
│
yes
│
v
Define success metrics
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.
- 8d ago First seen · 162 lines · 33 tokens per session scan A e945d1168847
engineering-manager is a skill published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,878 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
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
template-instantiation
Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…
Product Strategy
A comprehensive skill for product strategy — covering frameworks, opportunity sizing, prioritization, roadmap building, OKRs, and stakeholder management. From early-stage discovery to mature product org execution.
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
to-issues
A planning aid that breaks a PRD or technical specification into small implementation issues, each covering a complete, demonstrable piece of work.
handover-admin
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".