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 bestdeejay-design/agent-skills --skill repo-metadata-healthgit clone --depth 1 https://github.com/bestdeejay-design/agent-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/bestdeejay-design/agent-skills/repo-metadata-health)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/repo-metadata-health"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/repo-metadata-health/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/bestdeejay-design/agent-skills/repo-metadata-health"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/repo-metadata-health.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.00118 | $0.01055 |
| Opus 5 | $0.00059 | $0.00528 |
| Sonnet 5 | $0.00024 | $0.00211 |
| Haiku 4.5 | $0.00012 | $0.00105 |
Grade A, and why
repo-metadata-health 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 today.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Metadata Health — description, topics, Pages, community health
Use this skill to audit and update a repository's metadata and community health: description, topics, GitHub Pages link, homepage in About, and the Community Standards percentage. Keeps the GitHub page accurate after major changes.
When to use
- A repository's description/topics are outdated after a major change.
- Need the Community Health score (Community Profile API) audited against a 16-point checklist.
- GitHub Pages should be linked in README/About.
- User asks for "repo description", "repo topics", "github pages", "community health", "repo audit", "repo checklist".
Do NOT use
- For README content/visual header/footer — use
repo-readme-assets. - For legal/community files (LICENSE, CONTRIBUTING, SECURITY, templates) — use
repo-community-files. - For the social preview PNG — use
repo-social-preview.
Files
SKILL.md— this filescripts/validate_repo.py— 16-point checklist (gh API + filesystem, auto-detect from git remote)references/community-checklist.md— the full 16-point checklist with check commandsexamples/repo-hygiene.yml— CI example wiring the checklist into a workflow
Description and topics
Set via gh api:
# Description (UI limit ~350 chars) — list ALL key components
gh repo edit --description "<full description with keywords>"
# Topics (array via -f 'names[]=...') — PUT only, full list replacement
gh api -X PUT repos/<owner>/<repo>/topics \
-f 'names[]=python' -f 'names[]=markdown' -f 'names[]=documentation' \
-f 'names[]=agents' -f 'names[]=skills' -f 'names[]=opencode'
Topic rules:
- max 20 topics per repository (GitHub limit)
- each topic: ≤ 50 chars, lowercase letters/digits/hyphens only
- include language/framework/DB/broker (key ones), architectural patterns, project type
- all significant components must be reflected in both description and topics
GitHub Pages
If Pages is enabled (gh api repos/<owner>/<repo>/pages):
- README must contain a working link
https://<owner>.github.io/<repo>/ - About "Website" field = Pages URL (
gh repo edit --homepage https://…)
What ships with it
5 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.
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.
- today Changed · +8 lines 40c90503f9ae
- 12d ago First seen · 89 lines · 118 tokens per session scan A 7ebc9fe0f32b
repo-metadata-health is a skill published in the GitHub repository bestdeejay-design/agent-skills (6 stars, last pushed yesterday), licensed MIT. It adds 118 tokens to every session and 1,055 once invoked, about $0.0006 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
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
workflow
Use when a task is too large for turn-by-turn orchestration and should run through the big-task workflow lane: system-wide changes, large migrations, repo-wide audits, high-confidence verification, or tasks explicitly asking to run a workflow. Claude Code uses native dynamic workflows; Codex, OpenCode, and Grok use…
skill-compiler
Automatic solved-to-skill compiler — detects novel task completions and autonomously drafts new SKILL.md files. Stolen from Hermes Agent's learning loop (NousResearch, 2026-05-11).
context-compactor
9-section context compression with analysis scratchpad. Adapted from Claude Code's /compact system (2026-03-31).
daemon-loop
Autonomous recurring agent tasks — converts workflows into persistent background daemons that run on intervals. Stolen from Boris Cherny's Claude Code /loop pattern (2026-03-31).