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 d-oit/rust-2026-template --skill privacy-firstgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/privacy-first)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/privacy-first"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/privacy-first/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/d-oit/rust-2026-template/privacy-first"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/privacy-first.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01118 |
| Opus 5.5 | $0.00029 | $0.00447 |
| Sonnet 5.5 | $0.00014 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
privacy-first 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privacy First
When to Activate
- User asks: "prevent emails", "remove personal data", "privacy check", "never use email"
- Before writing any new code,
Cargo.toml, config, or documentation file - During code review or quality gate checks
- When adding contact information to any file
Agent Workflow
1. Before Writing Any File
Before creating or editing any file, check for email patterns:
# Scan the file being edited for email patterns
grep -E '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}' <file> || true
2. Replacement Rules
| Context | Instead of | Use |
|---|---|---|
Cargo.toml authors |
authors = ["Name <[email protected]>"] |
authors = ["Name"] |
| README contact | [email protected] |
GitHub Issues link |
| CONTRIBUTING.md | [email protected] |
https://github.com/owner/repo/issues |
| Code of Conduct | [email protected] |
"Report via GitHub Issues" |
| Examples in tests | [email protected] |
[email protected] (test domain only) |
3. Rust-Specific Rules
Cargo.toml
# Bad
[package]
authors = ["Dominik Oswald <[email protected]>"]
# Good
[package]
authors = ["Dominik Oswald"]
README.md / CONTRIBUTING.md
# Bad
Contact: [email protected]
# Good
Report issues: https://github.com/owner/repo/issues
Rust source code
- Never hardcode email addresses in
const,static, orfnbodies - Use placeholder
example.comdomain only in#[cfg(test)]blocks - Keep
deny.tomland CI configs free of personal email addresses
4. Exceptions (Allowed)
The following are permitted and should NOT be flagged:
- Test data in
tests/or#[cfg(test)]using standard test domains:example.com,example.org,test.com
- URLs in documentation pointing to external services
- Git history (cannot modify)
- Skill reference files with generic examples (for demonstration)
Quality Gate Integration
Add to scripts/quality-gates.sh or CI:
# Scan for email patterns (exclude test data and git)
EMAIL_PATTERN='[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}'
EXCLUDE_PATTERN='example\.com|example\.org|test\.com|\.git|node_modules|target'
# Check source files
if grep -rE "$EMAIL_PATTERN" \
--include="*.rs" --include="*.toml" \
--include="*.yaml" --include="*.json" --include="*.md" . \
2>/dev/null | grep -vE "$EXCLUDE_PATTERN"; then
echo "ERROR: Email address detected in codebase"
exit 1
fi
What ships with it
1 file 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.
- 1mo ago Changed · -6 lines 0781b57f65fb
- 2mo ago First seen · 143 lines · 72 tokens per session scan A 948a98dc172a
privacy-first is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,118 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
review-backend
Performs a strict code review of Rust backend code (files, diffs, or snippets). Trigger whenever the user shares backend code (Rust, SQL) and asks for a review, feedback, or says "review this" — including partial snippets.
review-frontend
Performs a strict code review of the Svelte 5 frontend code (files, diffs, or snippets). Trigger whenever the user shares frontend code (Svelte, TypeScript, CSS) and asks for a review, feedback, or says "review this" — including partial snippets.
triage-review-finding
Verifies and triages a code review finding (from an AI review, audit doc, or human reviewer) against the actual codebase. Trigger when the user pastes a review comment/finding and asks to check, analyze, or evaluate whether it makes sense.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…