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 aaronnat23/disp8ch --skill github-repo-managementgit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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/aaronnat23/disp8ch/github-repo-management)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/github-repo-management"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/github-repo-management.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.00110 |
| Opus 5 | $0.00000 | $0.00055 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
github-repo-management 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.
What it actually says
GitHub Repo Management
Handle repository-level GitHub work such as labels, milestones, repo settings, and hygiene tasks.
Use when
- A user wants repo organization work, not just one issue or PR.
- Release preparation needs repo metadata, labels, milestones, or templates cleaned up.
Workflow
- Confirm the target owner and repository.
- Make small repo-management changes in a reversible order.
- Prefer explicit naming and consistent labels over clever structures.
- Summarize what changed and what still needs manual review.
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 · 14 lines · 0 tokens per session scan A f2beaba8cda9
github-repo-management is a skill published in the GitHub repository aaronnat23/disp8ch (99 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 110 tokens. 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 skills, from other repositories
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
clawdbot-release-check
Check for new OpenClaw releases and notify once per new version.