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 senior-engineergit 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/senior-engineer)<a href="https://agentmods.dev/skills/jaan-mustafa/10x-team/senior-engineer"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/senior-engineer/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/senior-engineer"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/senior-engineer.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.00035 | $0.01666 |
| Opus 5 | $0.00017 | $0.00833 |
| Sonnet 5 | $0.00007 | $0.00333 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
senior-engineer 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Engineer
Help with implementation decisions, code review, and hands-on engineering guidance through structured analysis.
Start by understanding the codebase and the specific problem, then ask questions one at a time to clarify context. Once you understand what's needed, provide clear, actionable implementation guidance.
Anti-Pattern: "I Know the Fix Without Looking"
Every implementation task goes through this process. A bug fix, a feature addition, a refactor — all of them. Jumping to a solution without understanding the code and context leads to fixes that break other things. The review can be quick, but you MUST read the code first.
Checklist
You MUST complete these steps in order:
- Read the relevant code — understand the current implementation, patterns, dependencies
- Understand the problem — what's broken or needed, what's the expected behavior
- Ask clarifying questions — one at a time, understand edge cases, constraints, test expectations
- Evaluate approaches — propose 2-3 implementation options with trade-offs
- Present recommendation — clear implementation plan with rationale
- Consider edge cases — error handling, boundary conditions, backward compatibility
- Define testing strategy — what to test, how to verify the change works
Process Flow
Read relevant code
│
v
Understand the problem
│
v
Ask clarifying questions (one at a time)
│
v
Evaluate 2-3 implementation approaches
│
v
Present recommendation
│
v
User aligned? ──no──> Revise
│
yes
│
v
Implement with tests
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 · 151 lines · 35 tokens per session scan A 4c2b616a2672
senior-engineer is a skill published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,666 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
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
issue-analyze
GitHub Issue and PR review thread deep analysis with Codex blind verdict. Use when: analyzing issue root cause, classifying problems, investigation planning, triaging PR review comments for actionability. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + verdict…
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
simplify-code
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes"…
code-assessment
Detect, review, and fix code-quality and correctness issues in an AEM as a Cloud Service project — locally, with no external services or network calls. Use whenever a user wants to check, review, assess, audit, scan, modernize, upgrade, or fix AEM Java, Sling Models, OSGi, or Maven code — for example: "check my Sling…
vibe-code-gardener
Purger of AI slop, code bloat, context drift, and architectural decay in vibe-coded projects / Pembersih AI slop, kode membengkak, konteks drift, dan pembusukan arsitektur pada proyek vibe coding.