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 glebis/claude-skills --skill publish-skillgit clone --depth 1 https://github.com/glebis/claude-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/glebis/claude-skills/publish-skill)<a href="https://agentmods.dev/skills/glebis/claude-skills/publish-skill"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/publish-skill/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/glebis/claude-skills/publish-skill"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/publish-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 3 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 3 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Agent Snooping · line 33 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00166 | $0.04008 |
| Opus 5 | $0.00083 | $0.02004 |
| Sonnet 5 | $0.00033 | $0.00802 |
| Haiku 4.5 | $0.00017 | $0.00401 |
Grade A, and why
publish-skill 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 8d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish Skill to Site
Automate the full pipeline for publishing a skill to the claude-skills-site Astro website.
Paths
- Skills repo:
~/ai_projects/claude-skills/ - Site repo:
~/ai_projects/claude-skills-site/ - Site skills:
~/ai_projects/claude-skills-site/src/content/skills/*.mdx - Site bundles:
~/ai_projects/claude-skills-site/src/content/bundles/*.mdx
Invocation
/publish-skill <skill-name> # New skill — generates a hero image by default
/publish-skill <skill-name> --update # Regenerate existing .mdx (+ hero image)
/publish-skill <skill-name> --dry-run # Show what would be written, no commits, no image
/publish-skill <skill-name> --no-image # Skip hero-image generation
Workflow
Execute these phases in order. Stop and report on any error.
Phase 1 — Locate and Read Source
- Check
~/ai_projects/claude-skills/<skill-name>/SKILL.mdexists. Also check~/.claude/skills/<skill-name>/SKILL.md. - If neither exists, report error: "SKILL.md not found for
<skill-name>. Ensure the skill directory exists in the skills repo or ~/.claude/skills/." - If both exist, compare them. If
~/.claude/skills/version is newer (by mtime), sync it to the skills repo withrsync -av --exclude='*.egg-info' --exclude='__pycache__', commit the change, and push. This ensures the skills repo always has the latest version. - Read the SKILL.md (preferring the skills repo copy after any sync). Extract:
namefrom YAML frontmatterdescriptionfrom YAML frontmatter- Body content (everything after the frontmatter closing
---)
- Also check if
~/ai_projects/claude-skills/<skill-name>/README.mdexists — if so, read it for supplementary context.
Phase 2 — Check for Existing MDX
- Check if
~/ai_projects/claude-skills-site/src/content/skills/<skill-name>.mdxalready exists. - If it exists and
--updatewas NOT passed: stop and ask for confirmation. "The skill<skill-name>already has an .mdx on the site. Pass--updateto regenerate, or confirm to overwrite." - If it exists and
--updatewas passed: read the existing .mdx. Preserve these fields from the existing file (do not regenerate):apothecary_namehero_imageauto_activityauto_last_synced(will be updated to today)
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.
- 8d ago First seen · 285 lines · 166 tokens per session scan A b889a3b663f1
publish-skill is a skill published in the GitHub repository glebis/claude-skills (375 stars, last pushed 10d ago), licensed MIT. It adds 166 tokens to every session and 4,008 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…