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 PrabhdeepSingh/claude-plugins --skill securitygit clone --depth 1 https://github.com/PrabhdeepSingh/claude-pluginsWrote 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/prabhdeepsingh/claude-plugins/security)<a href="https://agentmods.dev/skills/prabhdeepsingh/claude-plugins/security"><img src="https://agentmods.dev/badge/skills/prabhdeepsingh/claude-plugins/security/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/prabhdeepsingh/claude-plugins/security"><img src="https://agentmods.dev/badge/skills/prabhdeepsingh/claude-plugins/security.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.00102 | $0.02620 |
| Opus 5.5 | $0.00041 | $0.01048 |
| Sonnet 5.5 | $0.00020 | $0.00524 |
| Haiku 4.5 | $0.00010 | $0.00262 |
Grade A, and why
security 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security — decide what can go wrong before deciding what to build
Security added after the design is a patch; security added at build time is a property. The cheapest moment to prevent a vulnerability is while the trust boundaries are still being drawn — before the upload handler exists, before the fetch reaches the network, before the dependency is installed. These rules make that moment explicit: name what can go wrong, gate the changes that widen the attack surface, and treat the classes of failure that recur everywhere — retried secrets, poisoned packages, model output in a sink — as design constraints, not review findings.
When to apply this
Any feature touching authentication or authorization, personal or payment data, file uploads, outbound requests to user-influenced destinations, new dependencies, webhooks or queues, or LLM/agent output feeding anything executable. The scoped mechanics stay with their owners — parameterized queries and boundary validation in [[code-standards]] §9, secret storage and CI credentials in [[infra-standards]] §3/§5 — this skill owns the decisions those mechanics assume were already made.
1. Threat-model first — five minutes, before any control
Before choosing defenses, name what's being defended. Three steps, time-boxed to minutes not meetings:
- Map the trust boundaries — every place outside data enters: HTTP requests, form fields, file uploads, webhooks, third-party API responses, queue messages, and LLM output (it's derived from inputs you don't control, so it's a boundary like any other).
- Name the assets — credentials, PII, payment data, admin capabilities, money movement. A boundary matters in proportion to what's reachable through it.
- Write abuse cases next to use cases. For each feature ask "how would I misuse this?" — then make that abuse the first test you write ([[tdd]]'s bug-fix reflex, applied before the bug exists). "Upload a profile photo" pairs with "upload a 2GB file", "upload an SVG with a script tag", "upload to someone else's profile".
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 · +1 lines d501a85eff88
- 1mo ago First seen · 94 lines · 102 tokens per session scan A 4a608961731d
security is a skill published in the GitHub repository PrabhdeepSingh/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 2,620 once invoked, about $0.0004 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
tg-account
A skill for using Telegram as the account owner through a local Telegram Desktop session. It can read chats and export messages, while writing actions require showing the target and exact text for confirmation.
unity-coder
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns.
agent-teams
Set up and orchestrate Claude Code agent teams - multiple Claude Code instances working together with shared tasks, inter-agent messaging, and centralized management. Use when the user wants to (1) create or start an agent team for parallel work, (2) configure agent team settings like display mode or teammate mode or…
python-coder
Implements Python code following PEP 8, type hints, and project conventions. Use when implementing features designed by python-architect.
python-testing
Python testing patterns with pytest including unit tests, integration tests, fixtures, mocking, and coverage. Use when writing Python tests.
typescript-coder
Implements TypeScript/JavaScript code following established architecture and coding guidelines. Use when implementing features designed by typescript-architect.