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.
/plugin marketplace add fvadicamo/dev-agent-skillsnpx agentmods add plugins/fvadicamo/dev-agent-skills/privacy-guardgit clone --depth 1 https://github.com/fvadicamo/dev-agent-skillsGrade A, and why
privacy-guard 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.
What it actually says
{
"name": "privacy-guard",
"description": "Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external contributors and in CI while gitleaks still covers generic secrets.",
"version": "1.3.3",
"author": {
"name": "Francesco Vadicamo",
"email": "[email protected]"
}
}
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 · 10 lines scan A fef3e5a4f5a2
privacy-guard is a plugin published in the GitHub repository fvadicamo/dev-agent-skills (72 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
coding
Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), and the Technical Project Plan workflow (tpp, handoff…
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
cpp
Two complementary modern-C++ (C++17) native-addon skills for Claude Code. resource-review traces object and resource lifetimes and reports only proven memory/resource defects (use-after-free, double-free, leaks, out-of-bounds, integer overflow, data races, Node-API handle/reference/threadsafe-function misuse), using a.
rust
A practical Rust project-setup skill for Claude Code. It creates, assesses, or improves stable Rust projects using profile-aware Cargo workspace and feature design, explicit edition/MSRV/toolchain policy, strict but usable rustc/Clippy/rustfmt configuration, layered testing and CI, idiomatic ownership and API design…
security
Complementary JavaScript/TypeScript web and Electron security skills for Claude Code. web-security-review traces data flow and reports only proven vulnerabilities. web-security-hardening assesses applicable OWASP ASVS 5.0.0 and Electron Security Checklist controls using evidence-backed Met/Gap/Not applicable/Needs…
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.