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-privacy)<a href="https://agentmods.dev/commands/kin9zeus/senior-engineer-skills/snr-privacy"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-privacy/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-privacy"><img src="https://agentmods.dev/badge/commands/kin9zeus/senior-engineer-skills/snr-privacy.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.01157 |
| Opus 5 | $0.00014 | $0.00579 |
| Sonnet 5 | $0.00006 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
snr-privacy 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privacy and Compliance Pack
Scope: $ARGUMENTS (default: the whole project, all four artefacts).
Load privacy-compliance. Load database-engineering for the erasure plan and
retention jobs.
Say once, plainly: this produces technical controls and a policy drafted from real data flows. It is not legal advice. For a regulated sector, children's data, or special-category data, recommend a qualified privacy lawyer review the output — then build the controls anyway, because they are the same either way.
The order is fixed
Each artefact depends on the one above it. Drafting a policy before the inventory means describing a system you have not read.
1 DATA INVENTORY from the CODE — schema, routes, third parties
2 POLICY generated from the inventory
3 CONSENT a mechanism that genuinely gates the scripts
4 RIGHTS PIPELINE export and deletion, automated end to end
5 GOVERNANCE DPAs, subprocessor list, retention jobs, breach plan
1 · The inventory — from the code, never from an interview
# Personal data in the schema
grep -rEni '(email|phone|address|birth|dob|ssn|passport|ip_?addr|location|gender|name)' \
--include='*.prisma' --include='*.sql' --include='models*.py' --include='schema.rb' . | head -40
# EVERY third party that receives data — the highest-yield check in a privacy audit
grep -rhoE 'googletagmanager|google-analytics|gtag\(|connect\.facebook\.net|hotjar|segment|mixpanel|posthog|intercom|clarity\.ms|sentry\.io|stripe|paypal|fonts\.googleapis|recaptcha|youtube\.com/embed' \
. --exclude-dir={node_modules,.git,dist} | sort -u
Every third party present in the code and absent from the policy is a P1.
It is a misrepresentation to users, not a documentation gap. Note that a font CDN
receives every visitor's IP address.
Then tag the schema so the inventory stays current rather than going stale in month two.
2 · The policy
Use templates/privacy-policy.md (EN) or templates/privacy-policy.es.md (ES).
Fill it from the inventory, delete every inapplicable section, and never:
claim a certification you do not hold, describe processing you do not do,
promise deletion you cannot perform, or state a retention period nothing
enforces.
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 · 115 lines · 28 tokens per session scan A 9942d2cf9b9c
snr-privacy 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 1,157 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
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.
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.
design-doc
Write a design doc / RFC as Markdown in the user's repository. Use when invoked as /document-design-system:design-doc. Produce designed HTML or PDF only when asked.
tutorial
Write a Diátaxis tutorial as Markdown in the user's repository. Use when invoked as /document-design-system:tutorial. Produce designed HTML or PDF only when asked.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.