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 vivy-yi/awesome-skills --skill metadata-enrichergit clone --depth 1 https://github.com/vivy-yi/awesome-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/vivy-yi/awesome-skills/metadata-enricher)<a href="https://agentmods.dev/skills/vivy-yi/awesome-skills/metadata-enricher"><img src="https://agentmods.dev/badge/skills/vivy-yi/awesome-skills/metadata-enricher/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/vivy-yi/awesome-skills/metadata-enricher"><img src="https://agentmods.dev/badge/skills/vivy-yi/awesome-skills/metadata-enricher.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.00105 | $0.02095 |
| Opus 5 | $0.00053 | $0.01047 |
| Sonnet 5 | $0.00021 | $0.00419 |
| Haiku 4.5 | $0.00011 | $0.00210 |
Grade A, and why
metadata-enricher scanned grade A with 1 finding 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 12d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run( How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata Enricher
Enriches skills.json with additional metadata fields for better categorization and filtering.
Target Metadata Schema
{
"name": "owner/repo",
"stars": 1234,
"desc": "Description",
"url": "https://github.com/owner/repo",
"category": "code-review", // NEW: primary category
"tags": ["security", "claude"], // NEW: searchable tags
"license": "MIT", // NEW: license type
"language": "Python", // NEW: primary language
"added_date": "2026-04-20", // NEW: when added to collection
"last_updated": "2026-04-25", // NEW: last star/meta update
"source": "trending" // NEW: discovery method
}
Workflow
1. Define Category Taxonomy
cd /Volumes/waku/github-维护/awesome/awesome-skills-repos && \
cat << 'EOF'
CATEGORIES:
- code-review # Code quality, security, testing
- web-development # Frontend, backend, APIs
- data-science # ML, AI, analytics, notebooks
- devops # CI/CD, infrastructure, containers
- mobile # iOS, Android, React Native
- productivity # Writing, notes, task management
- platform-integration # GitHub, Slack, Jira, Feishu
- content-creation # Blog, social media, video
- research # Papers, academic, knowledge
- framework # Agentic frameworks, orchestration
- skill-tools # Skills creation/maintenance tools
- database # SQL, NoSQL, data storage
- security # Cybersecurity, auth, encryption
- other # Uncategorized
TAGS (auto-detectable):
- claude-code, cursor, opencode, codex # Platform-specific
- python, typescript, rust, go # Language
- mcp, api, cli, agent # Tech type
- awesome, list, collection # List type
- security, review, test # Function
- chinese, english # Language of docs
EOF
2. Enrich All Repos via GitHub API
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.
- 12d ago First seen · 237 lines · 0 tokens per session scan A 62c3a8a43094
metadata-enricher is a skill published in the GitHub repository vivy-yi/awesome-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 105 tokens to every session and 2,095 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…