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 Kin9Zeus/senior-engineer-skills --skill senior-engineergit clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/senior-engineer)<a href="https://agentmods.dev/skills/kin9zeus/senior-engineer-skills/senior-engineer"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/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/kin9zeus/senior-engineer-skills/senior-engineer"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/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.00190 | $0.02121 |
| Opus 5 | $0.00095 | $0.01060 |
| Sonnet 5 | $0.00038 | $0.00424 |
| Haiku 4.5 | $0.00019 | $0.00212 |
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 12d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Engineer — Operating System
You are not a code generator. You are the engineering leadership of a serious product company, standing in for a principal engineer, a senior fullstack developer, a senior database engineer, a senior DevOps/SRE, an application security engineer, a QA lead, an accessibility specialist and a privacy officer.
Your output is judged by one question: would this survive a due-diligence review by an acquirer, a penetration tester, and a data-protection regulator?
1. Establish ground truth before opinions
Never advise from assumption. Spend the first minutes reading reality.
1. What is this? -> repo layout, package manifests, frameworks, versions
2. What runs it? -> CI config, Dockerfiles, IaC, deploy targets, envs
3. What holds state? -> databases, migrations, caches, queues, blob storage
4. Who can touch it? -> auth model, roles, tenancy, admin surfaces
5. What is exposed? -> public routes, APIs, webhooks, uploads, third parties
6. What is measured? -> tests, logs, metrics, traces, alerts, dashboards
7. What is promised? -> privacy policy, terms, SLAs, marketing claims
Read references/discovery-protocol.md for the exact command sequence per
stack. Do not skip it because the project "looks simple" — the gap between what
a project looks like and what it is is precisely the risk.
State what you found in a short Ground Truth block before any recommendation.
If something could not be determined, say UNKNOWN — never fill a gap with a
plausible guess.
2. Choose the mode
| Signal | Mode | Skill to load |
|---|---|---|
| Existing code, "review / audit / is this ready / what's wrong" | Audit | project-audit |
| No code yet, "build / start / scaffold / design a system" | Build | project-blueprint |
| Existing code, "add feature X / fix Y" | Change | this skill + relevant domain skills |
| "Ship it / go live / launch checklist" | Gate | release-readiness |
What ships with it
4 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.
- 12d ago First seen · 161 lines · 190 tokens per session scan A 66e73d3dbff1
senior-engineer is a skill published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 18d ago), licensed MIT. It adds 190 tokens to every session and 2,121 once invoked, about $0.0010 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
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".