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 ayalaphiscan/web-security-guard --skill sicurezza-githubgit clone --depth 1 https://github.com/ayalaphiscan/web-security-guardWrote 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/ayalaphiscan/web-security-guard/sicurezza-github)<a href="https://agentmods.dev/skills/ayalaphiscan/web-security-guard/sicurezza-github"><img src="https://agentmods.dev/badge/skills/ayalaphiscan/web-security-guard/sicurezza-github/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/ayalaphiscan/web-security-guard/sicurezza-github"><img src="https://agentmods.dev/badge/skills/ayalaphiscan/web-security-guard/sicurezza-github.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.00118 | $0.00903 |
| Opus 5.5 | $0.00047 | $0.00361 |
| Sonnet 5.5 | $0.00024 | $0.00181 |
| Haiku 4.5 | $0.00012 | $0.00090 |
Grade A, and why
sicurezza-github 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sicurezza GitHub · GitHub Security
🇮🇹 Versione italiana qui sotto · 🇬🇧 English version below
Quando un progetto ha (o avrà) una repository GitHub, installare i file di sicurezza nella directory .github/ della repo. I template pronti sono in references/.
File da installare nella repo
.github/workflows/security.yml— dareferences/security-workflow.yml: a ogni push/PR e ogni notte esegue scansione segreti (Gitleaks), audit dipendenze (npm/pip) e analisi statica CodeQL..github/dependabot.yml— dareferences/dependabot.yml: PR automatiche di aggiornamento per dipendenze vulnerabili.
Adattare al linguaggio del progetto: lasciare il job npm audit solo se c'è package.json, pip-audit solo se c'è requirements.txt/pyproject.toml, impostare i linguaggi CodeQL corretti (javascript, python, ecc.).
Regole
- Verificare che
.gitignoreescluda.enve credenziali PRIMA del primo push. Se un segreto è già finito nella history, va considerato compromesso: ruotarlo subito (cambiare la chiave dal provider), non basta cancellare il file. - Consigliare all'utente di attivare nelle impostazioni GitHub della repo: Secret scanning + Push protection, Dependabot alerts, branch protection sul branch principale (review obbligatoria, status check del workflow security).
- I workflow falliscono la build se trovano segreti o vulnerabilità high/critical: spiegare all'utente che è voluto.
Limite da comunicare
Questi workflow proteggono il codice e le dipendenze, non bloccano gli attacchi al sito in esecuzione: per quello servono la skill difesa-attacchi (middleware) e un WAF/CDN davanti al sito.
GitHub Security (English)
When a project has (or will have) a GitHub repository, install the security files in the repo's .github/ directory. Ready-made templates are in references/.
Files to install in the repo
.github/workflows/security.yml— fromreferences/security-workflow.yml: on every push/PR and nightly, runs secret scanning (Gitleaks), dependency audit (npm/pip) and CodeQL static analysis..github/dependabot.yml— fromreferences/dependabot.yml: automatic update PRs for vulnerable dependencies.
What ships with it
2 files 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.
- 1mo ago First seen · 47 lines · 118 tokens per session scan A 214657ae42fa
sicurezza-github is a skill published in the GitHub repository ayalaphiscan/web-security-guard (4 stars, last pushed 4mo ago), licensed MIT. It adds 118 tokens to every session and 903 once invoked, about $0.0005 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
ponytail-sec-audit
Full project security audit. Scans the entire codebase across three passes: code that shouldn't exist, all dependencies assessed, all security findings. Produces a comprehensive numbered report with blast-radius narrative. Persists findings to .ponytail-sec/ for cross-scan tracking. For per-diff review use…
ponytail-sec
Security companion for active development. Scopes to the current diff or changed files. Three passes: YAGNI code review, new-dep assessment, and up to 3 material security findings. Lean by design — surfaces the one thing to fix before merging, not a backlog. Use ponytail-sec-audit for a full project scan.
k8s-securitycontext
Binary Kubernetes securityContext hardening check. Use when reviewing Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, Helm templates, or Kubernetes manifests that define containers. Minimal output only: OK or NOTOK: RULE, RULE.
dockerfile
Binary Dockerfile image-build hardening check. Use when reviewing Dockerfiles, container image builds, multi-stage builds, runtime users, pinned bases, or reproducible dependency installs. Minimal output only: OK or NOTOK: RULE, RULE.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
review
5-pass structured code review — correctness, security, performance, readability, consistency.