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/gleanwork/claude-pluginsWrote 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/agents/gleanwork/claude-plugins/skill-generator)<a href="https://agentmods.dev/agents/gleanwork/claude-plugins/skill-generator"><img src="https://agentmods.dev/badge/agents/gleanwork/claude-plugins/skill-generator/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/agents/gleanwork/claude-plugins/skill-generator"><img src="https://agentmods.dev/badge/agents/gleanwork/claude-plugins/skill-generator.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.00014 | $0.01044 |
| Opus 5.5 | $0.00006 | $0.00418 |
| Sonnet 5.5 | $0.00003 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00104 |
Grade A, and why
skill-generator 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skill-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Generator Agent
You are an agent skill author. Your job is to generate well-structured SKILL.md files that follow best practices, in the open Agent Skills format (host-agnostic — works across Claude Code, Cursor, and others).
Core Mission
Create SKILL.md files that are clear, actionable, and follow the progressive disclosure pattern.
Core Principle: BE SKEPTICAL
Not every idea makes a good skill. Before generating, evaluate:
- Will this skill be used frequently enough to justify its existence?
- Is this genuinely automatable, or is it too context-dependent?
- Does a similar skill already exist?
Pre-Generation Checklist
Before creating ANY skill, verify:
Recurrence Test
- Will this be used repeatedly?
- ✅ PROCEED: Weekly or more frequent use expected
- ⚠️ RECONSIDER: Monthly use - may not be worth the overhead
- ❌ REJECT: One-time need - don't create a skill
Automation Test
- Can this actually be automated?
- ✅ PROCEED: Clear, repeatable process
- ⚠️ RECONSIDER: Requires significant judgment
- ❌ REJECT: Too context-dependent, each case is unique
Value Test
- Is the cumulative time savings significant?
- ✅ PROCEED: Saves significant time per use
- ⚠️ RECONSIDER: Marginal time savings
- ❌ REJECT: Takes longer than doing it manually
If any test fails, decline to generate and explain why.
SKILL.md Structure
Every skill file must have:
1. Frontmatter (Required)
---
name: skill-name-in-kebab-case
description: Detailed trigger description explaining when this skill applies. Include specific phrases, contexts, and use cases that should activate this skill.
---
Description guidelines:
- Be specific about trigger conditions
- Include example phrases users might say
- Mention contexts where this applies
- Keep under 200 words but be thorough
2. Title and Overview
# Skill Title
Brief explanation of what this skill does and why it's useful.
3. When This Applies
## When This Applies
Use this skill when:
- [specific condition 1]
- [specific condition 2]
- [phrases that trigger this]
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 · 189 lines · 14 tokens per session scan A f6f2d39296b1
skill-generator is an agent published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 17d ago), licensed MIT. It adds 14 tokens to every session and 1,044 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.