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.
git 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/commands/kin9zeus/senior-engineer-skills/snr-scorecard)<a href="https://agentmods.dev/commands/kin9zeus/senior-engineer-skills/snr-scorecard"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-scorecard/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/commands/kin9zeus/senior-engineer-skills/snr-scorecard"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-scorecard.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.00028 | $0.00868 |
| Opus 5 | $0.00014 | $0.00434 |
| Sonnet 5 | $0.00006 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
snr-scorecard 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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Scorecard
Score: $ARGUMENTS (default: the current repository).
This is the fast assessment — one screen, a number, and the three things to
fix first. For the full findings report with reproductions and fixes, use
/snr-audit.
Load senior-engineer for the rubric in
references/severity-and-reporting.md.
Gather evidence quickly
skills/project-audit/scripts/recon.sh # read-only, ~30 seconds
skills/security-hardening/scripts/secret-scan.sh
skills/web-presence-audit/scripts/web-check.sh <url> # if there is a live site
Then the seven high-yield checks from
project-audit/references/quick-scan.md: secrets, authorization on the hottest
routes, injection, data survivability, public surface, correctness signal, and
honest promises.
Score
Fifteen domains, 0–10 each, weighted to 100.
| # | Domain | Wt | # | Domain | Wt |
|---|---|---|---|---|---|
| 1 | Security | 15 | 9 | Accessibility | 6 |
| 2 | Data & persistence | 12 | 10 | Web presence & SEO | 5 |
| 3 | Correctness & testing | 11 | 11 | Privacy & compliance | 6 |
| 4 | Architecture | 10 | 12 | Documentation | 4 |
| 5 | API design | 7 | 13 | Dependencies & supply chain | 5 |
| 6 | DevOps & delivery | 8 | 14 | Developer experience | 4 |
| 7 | Observability | 7 | 15 | Cost & scalability | 4 |
| 8 | Performance | 6 |
Bands — 0–39 Critical · 40–59 At risk · 60–74 Functional · 75–89 Professional · 90–100 Exemplary
Output — one screen
## <Project> — Engineering Scorecard <commit> · <date>
# 58/100 — At risk
**Weakest:** Privacy 2/10 · Observability 3/10 · Testing 4/10
| Domain | Score | Evidence |
|---|---:|---|
| Security | 6/10 | Headers set, deps current. No rate limit on /login (`auth.ts:41`) |
| Data | 7/10 | Migrations reversible. Backups configured but never restored |
| Testing | 4/10 | 31 unit tests, no integration or E2E. CI does not block |
| ... | | |
## Fix these three first
1. **No privacy policy, and PostHog + Intercom receive personal data** —
`P0`, legal exposure from day one. ~4h.
2. **Backups never restored** — `P1`, recovery capability is unverified. ~1d.
3. **No error tracking** — `P1`, faults are invisible. ~2h.
## Blockers for launch
<the P0 list, or "none">
## Not assessed
<explicit — this section is mandatory>
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.
- 11d ago First seen · 89 lines · 28 tokens per session scan A 5f62b5aecc23
snr-scorecard is a command published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 28 tokens to every session and 868 once invoked, about $0.0001 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 commands, from other repositories
scaffold-project
Scaffold a new design-product project that matches the recommended Claude Code layout (the reference structure). Use when starting a fresh product/app that will be built with this design system.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
gate
Run the one-command quality gate and report the real N/N result. Use before claiming any build/review is done.
ship
Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
code-review
OWASP-mapped, skill-aware code review with autofix suggestions. Reviews the diff, not the world.
adr
Write an architecture decision record as Markdown in the user's repository. Use when invoked as /document-design-system:adr. Produce designed HTML or PDF only when asked.