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 urmzd/dotfiles --skill update-repo-metagit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/update-repo-meta)<a href="https://agentmods.dev/skills/urmzd/dotfiles/update-repo-meta"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/update-repo-meta/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/urmzd/dotfiles/update-repo-meta"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/update-repo-meta.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.00100 | $0.00612 |
| Opus 5 | $0.00050 | $0.00306 |
| Sonnet 5 | $0.00020 | $0.00122 |
| Haiku 4.5 | $0.00010 | $0.00061 |
Grade A, and why
update-repo-meta 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 9d 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.
What it actually says
Update Repo Meta
Update GitHub repository metadata.
Steps
-
Read current state:
gh repo view --json name,description,homepageUrl,repositoryTopics,visibility -
Determine changes: Based on the user's argument or conversation context, figure out what to update. Common operations:
- Topics:
gh repo edit --add-topic <topic>or--remove-topic <topic> - Description:
gh repo edit --description "<text>" - Homepage:
gh repo edit --homepage "<url>" - Visibility:
gh repo edit --visibility public|private
- Topics:
-
Apply changes: Run the appropriate
gh repo editcommands. -
Verify: Run
gh repo view --json name,description,homepageUrl,repositoryTopics,visibilityagain and show the updated state.
Rules
- Show the before/after so the user can confirm the changes.
- If no specific instructions are given, show the current metadata and ask what to change.
- Topics should be lowercase, hyphenated (e.g.,
cli-tool,go,mcp-server).
Gotchas
- Topic cap is 20. GitHub caps a repo at 20 topics;
gh repo edit --add-topicpast that limit fails. Check the current count before adding in bulk. - Server-side normalization is authoritative. GitHub lowercases topics and replaces
spaces/invalid characters with hyphens on its end. Normalizing client-side first is only
cosmetic; the server has the final say, so verify with
gh repo viewrather than assuming your input string was stored verbatim. - Visibility changes can be blocked.
gh repo edit --visibilitymay require an explicit consent flag (e.g.--accept-visibility-change-consequences), and an org policy can block going public or private entirely. If the command errors, surface the policy/consent reason to the user rather than retrying blindly.
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.
- 9d ago First seen · 54 lines · 100 tokens per session scan A 09c911aa3820
update-repo-meta is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 100 tokens to every session and 612 once invoked, about $0.0005 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
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.
gen-commit-msg
Generate intelligent commit messages based on staged changes following Conventional Commits format.