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.
git clone --depth 1 https://github.com/photostructure/coding-skillsWrote 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/plugins/photostructure/coding-skills/security)<a href="https://agentmods.dev/plugins/photostructure/coding-skills/security"><img src="https://agentmods.dev/badge/plugins/photostructure/coding-skills/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/plugins/photostructure/coding-skills/security"><img src="https://agentmods.dev/badge/plugins/photostructure/coding-skills/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
What it actually says
{
"name": "security",
"version": "1.2.2",
"description": "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 verification states.",
"author": {
"name": "Matthew McEachen",
"url": "https://photostructure.com/coding/"
},
"homepage": "https://photostructure.com/coding/",
"license": "CC-BY-SA-4.0",
"keywords": [
"claude-code",
"skills",
"security",
"security-review",
"owasp",
"javascript",
"typescript",
"web-security",
"security-hardening",
"security-best-practices",
"asvs",
"csp",
"self-hosted",
"oidc",
"docker",
"electron",
"desktop-security"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 300 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 First seen · 31 lines scan A 6b0a1af5cbe2
security is a plugin published in the GitHub repository photostructure/coding-skills (4 stars, last pushed 13d 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-31.
Other plugins, from other repositories
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
privacy-guard
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…
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
pr-sweep
Cross-repo PR sweep: triage all open PRs, run code reviews, merge what's ready, fix quick CI blockers, and report.
review
Code review for a branch, PR, or path — structured output with severity labels and cross-file analysis.
frontend-craft
A shared add-on for frontend development teams, with frontend instructions, helper agents, automated hooks, and connections to design tools such as Figma and Sketch. It saves reports as Markdown files.