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 agentmods add skills/d-oit/rust-2026-template/privacy-firstnpx 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.svg" alt="Measured on agentmods" 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 | $0.00072 | $0.01160 |
| Opus 5 | $0.00036 | $0.00580 |
| Sonnet 5 | $0.00014 | $0.00232 |
| Haiku 4.5 | $0.00007 | $0.00116 |
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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Privacy First
When to Use
- User asks for this skill's functionality
This skill ensures no email addresses or personal data leak into the Rust codebase. It provides detection, prevention, and automated checking for Rust projects.
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)
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.
- 3d 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 (10 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 1,160 once invoked, about $0.0004 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
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
starter-cleaner
将 wot-starter v2 模板精简为最小可开发状态，移除文档、演示分包、生成文件和 monorepo 配置，并同步清理相关 Vite 与 package.json 配置。用户要求“清理模板”“移除示例”“生成最小模板”“精简 wot-starter v2”时使用。.
wot-ui-cli
回答、使用、调试 @wot-ui/cli 时使用。关键词：wot、@wot-ui/cli、CLI、MCP、doctor、usage、lint、list、info、doc、demo、token、changelog、extract、wot mcp。适用于命令查询、参数说明、MCP 接入、本地调试、数据提取与 open-wot 仓库维护。.
better-auth-best-practices
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables. Use when users mention Better Auth, betterauth, auth.ts, or need to set up TypeScript authentication with email/password, OAuth, or plugin configuration.
supabase-rls
Supabase RLS 政策規範。Use when creating or modifying RLS policies (CREATE POLICY, ALTER POLICY), setting up Row Level Security, or working with database access control. Always use this skill for RLS design, policy templates, and role-based access patterns.
verify-ui
Verify UI implementation against Stitch design via a token audit (HTML ↔ Code, with X-component default-render checks) and an X-components compliance check.