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/openops-studio/vibe-driven-dev/privacy-checknpx skills add OpenOps-Studio/vibe-driven-dev --skill privacy-checkgit clone --depth 1 https://github.com/OpenOps-Studio/vibe-driven-devWrote 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/openops-studio/vibe-driven-dev/privacy-check)<a href="https://agentmods.dev/skills/openops-studio/vibe-driven-dev/privacy-check"><img src="https://agentmods.dev/badge/skills/openops-studio/vibe-driven-dev/privacy-check.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.00040 | $0.00243 |
| Opus 5 | $0.00020 | $0.00121 |
| Sonnet 5 | $0.00008 | $0.00049 |
| Haiku 4.5 | $0.00004 | $0.00024 |
Grade A, and why
privacy-check 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 26 lines · 40 tokens per session scan A 94e512f1b648
privacy-check is a skill published in the GitHub repository OpenOps-Studio/vibe-driven-dev (1 stars, last pushed 5mo ago), with no licence file. It adds 40 tokens to every session and 243 once invoked, about $0.0002 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
privacy-check
Evaluates product assumptions and plans for PII handling, user tracking, and data retention risks. Triggered during 'research' and 'blueprint' stages to enforce privacy-by-design.
security-gate
Evaluates project artifacts and state for security risks. Triggered explicitly before the 'scaffold' and 'qa' stages to ensure no hardcoded secrets, unsafe dependency assumptions, or major architectural security flaws pass into execution.
input-validation
Validates all raw external inputs (commands, configuration overrides) provided to the VDD runtime to prevent path traversal, prototype pollution, or injection.
prompt-integrity
Verifies the structure, safety, and guardrails of system prompts generated within the project to prevent unintended behavior, hallucination, and prompt injection.
mcp-urgent-caller-triage
Prioritize inbound client calls by reading transcripts, classifying urgency, matching callers to legal client and matter context, and preparing a callback list for human review.
git-guardrails
Use this skill to enforce strict safety boundaries on git operations, branch management, and destructive shell commands. Prevents accidental force pushes, hard resets, secret commits, unstashed code loss, and unauthorized production branch modifications.