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-rotate)<a href="https://agentmods.dev/commands/kin9zeus/senior-engineer-skills/snr-rotate"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-rotate/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-rotate"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-rotate.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.00033 | $0.00491 |
| Opus 5.5 | $0.00013 | $0.00196 |
| Sonnet 5.5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
snr-rotate 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 2d 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.
What it actually says
Secret Rotation
Rotate: $ARGUMENTS (default: every secret the project and its platform hold).
Load security-incident-response (and cloud-security for the long-term fix).
Rotation changes live credentials — propose the plan, get the user's confirmation,
then execute step by step. Never print or paste secret values.
Steps
-
Inventory (names only).
bash skills/security-incident-response/scripts/rotation-inventory.sh .(PowerShell:.ps1). Then ask the user for what the script cannot see: provider dashboards, CI variable stores, preview/staging environments, laptops. -
Fill
templates/rotation-tracker.md, ordered by blast radius: cloud/IAM → database → signing & encryption keys → payments → spend-bearing APIs (AI, SMS, email) → OAuth/webhooks → registries/CI → the rest. -
For each secret, apply the universal procedure:
create new at the ISSUER → distribute → deploy → revoke old → prove old is dead → record. Per-provider notes and consequences (session secrets, framework app keys, JWT signing) are inreferences/secret-rotation-playbook.md— read the consequences row before rotating signing or encryption keys. -
Verify every row: call with the old value and expect
401/403. A dashboard edit alone is not a rotation. -
Narrow while you are here — new credentials get least privilege, a network restriction, a spend cap and a label (
cloud-security). -
Hunt at each issuer for use during the exposure window (
references/detection-and-hunting.md).
Output
- The completed tracker (names and ids only — never values)
- Rotations that could not be completed, with owner and deadline
- Copies found that were not on the list
- What I could not verify — 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.
- 2d ago First seen · 46 lines · 33 tokens per session scan A 8e14be326d13
snr-rotate is a command published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 491 once invoked, about $0.0001 per session on Opus 5.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-10-24.
Other commands, from other repositories
gate
Run every objective gate this project can prove and report the real N/N. Use before claiming any screen or component is done.
compose
Compose a document from a reading pattern when no canonical type fits, as Markdown in the user's repository. Use when invoked as /document-design-system:compose. Produce designed HTML or PDF only when asked.
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.
test-report
Write a point-in-time test report as Markdown in the user's repository. Use when invoked as /document-design-system:test-report. Produce designed HTML or PDF only when asked.
change-request
Write a change request as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
estimate
Write a basis of estimate as Markdown in the user's repository. Produce designed HTML or PDF only when asked.