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 Jewgah/claude-code-skills --skill vulgarizegit clone --depth 1 https://github.com/Jewgah/claude-code-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/skills/jewgah/claude-code-skills/vulgarize)<a href="https://agentmods.dev/skills/jewgah/claude-code-skills/vulgarize"><img src="https://agentmods.dev/badge/skills/jewgah/claude-code-skills/vulgarize/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/jewgah/claude-code-skills/vulgarize"><img src="https://agentmods.dev/badge/skills/jewgah/claude-code-skills/vulgarize.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.00033 | $0.00869 |
| Opus 5 | $0.00016 | $0.00434 |
| Sonnet 5 | $0.00007 | $0.00174 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
vulgarize 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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulgarize — plain-language summary of what changed
Produce a simple message for a non-technical client summarising the code changes. It reads like the developer texting the client directly, not like a release note.
Language: en by default. If $ARGUMENTS starts with fr, write it in French, casual and
informal (tutoiement, no polite formulas). Everything else below is identical.
Sibling skill:
/explain-devproduces a structured WhatsApp update (bold numbered points + a numbered "How to test" section). This one produces a flowing, casual text message. Pick by how formal the recipient is.
Steps
- Read the changes: look at the git diff (staged + unstaged) and recent commits to understand what actually changed.
- Find the "why": for each change, identify the concrete impact for the user or the business.
- Write the message following the rules below.
Writing rules
- First person, speaking directly to them: "I did…", "I added…" — as if you are the developer talking TO the client. Never refer to the client in the third person ("the client asked…"). Say "you mentioned that…" when referencing feedback you got.
- No technical jargon: no file names, function names, variable names, component names. Ever.
- Casual tone: like a WhatsApp/Slack message. No formal salutations, no sign-off boilerplate.
- Explain the WHY, not just the what: e.g. "that way the numbers are frozen at the moment the order is accepted, so they can't drift afterwards".
- Group logically: merge related changes into one flowing explanation rather than listing them file by file.
- If a technical concept is unavoidable, explain it in parentheses: "a snapshot (a frozen copy)".
- No bullet lists, no markdown: plain text, it's a message not a document.
- Short and direct: no "here's what I did" preamble. Get straight to it.
- NEVER use an em dash (—), en dash (–) or arrow (→) — they read as AI-written. Use a comma, a period, parentheses, or the word "to" instead.
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.
- 11d ago First seen · 76 lines · 33 tokens per session scan A bedb647b431c
vulgarize is a skill published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 869 once invoked, about $0.0002 per session on Opus 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…