sicurezza-github

sicurezza-github is a skill for Claude Code from ayalaphiscan/web-security-guard. It costs 118 tokens per session (903 once invoked), scanned A, original, MIT.

A set of GitHub security workflows for scanning code repositories for leaked secrets, vulnerable dependencies, and certain code problems.

In plain words
What is it for?
Add workflows for Gitleaks secret scanning, npm or Python dependency audits, CodeQL static analysis, and Dependabot updates.
Why use it?
It automates recurring security checks and dependency update work in GitHub.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the web-security-guard plugin — 6 skills, 2 commands shipped together

Good fit Add workflows for Gitleaks secret scanning, npm or Python dependency audits, CodeQL static analysis, and Dependabot updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ayalaphiscan/web-security-guard/sicurezza-github
Install

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.

Any agent
npx skills add ayalaphiscan/web-security-guard --skill sicurezza-github
Clone the repo
git clone --depth 1 https://github.com/ayalaphiscan/web-security-guard

Made for: Claude Code.

Or install web-security-guard, the plugin that ships this one along with the rest of its 6 skills, 2 commands.

Wrote 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.

agentmods badge for sicurezza-github

README.md
[![agentmods](https://agentmods.dev/badge/skills/ayalaphiscan/web-security-guard/sicurezza-github/github.svg)](https://agentmods.dev/skills/ayalaphiscan/web-security-guard/sicurezza-github)
Your own site
<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.

agentmods 80×15 button for sicurezza-github

Your own site · 80×15
<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>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 903 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 214657ae42fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/sicurezza-github/SKILL.md · 47 lines

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

  1. .github/workflows/security.yml — da references/security-workflow.yml: a ogni push/PR e ogni notte esegue scansione segreti (Gitleaks), audit dipendenze (npm/pip) e analisi statica CodeQL.
  2. .github/dependabot.yml — da references/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 .gitignore escluda .env e 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

  1. .github/workflows/security.yml — from references/security-workflow.yml: on every push/PR and nightly, runs secret scanning (Gitleaks), dependency audit (npm/pip) and CodeQL static analysis.
  2. .github/dependabot.yml — from references/dependabot.yml: automatic update PRs for vulnerable dependencies.

Read the full file on GitHub · 47 lines

Files

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.

Changes

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.

  1. 1mo ago First seen · 47 lines · 118 tokens per session scan A 214657ae42fa

Subscribe to this mod's changes

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.

Related

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…

andypitcher/ponytail-sec · 73 tokens

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.

andypitcher/ponytail-sec · 73 tokens

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.

andypitcher/ponytail-sec · 57 tokens

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.

andypitcher/ponytail-sec · 51 tokens

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

review

5-pass structured code review — correctness, security, performance, readability, consistency.

SethGammon/Citadel · 17 tokens