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 elevanaltd/HestAI-MCP --skill github-labelsgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/github-labels)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/github-labels"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/github-labels/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/elevanaltd/hestai-mcp/github-labels"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/github-labels.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.00021 | $0.01000 |
| Opus 5.5 | $0.00008 | $0.00400 |
| Sonnet 5.5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
github-labels 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Labels Skill
Purpose
Prevents "label not found" errors when creating GitHub issues by providing agents with the current valid label taxonomy.
Valid Labels (Current Repository)
Standard Labels
bug- Something isn't workingdocumentation- Improvements or additions to documentationduplicate- This issue or pull request already existsenhancement- New feature or requestgood first issue- Good for newcomershelp wanted- Extra attention is neededinvalid- This doesn't seem rightquestion- Further information is requestedwontfix- This will not be worked on
Document Types
adr- Architecture Decision Recordrfc- Request for Comments (deprecated per ADR-0060)
Priority Levels
priority:p0-critical- Blocking production or critical pathpriority:p1-high- Important, should be addressed soonpriority:p2-medium- Normal prioritypriority:p3-low- Nice to have
Development Phases
phase:b1- B1: Foundation phasephase:b2- B2: Features phasephase:future- Future consideration
Area Tags
area:mcp-tools- MCP tool implementationarea:governance- Governance systemarea:ci-cd- CI/CD pipelinearea:agents- Agent system
Status Tags
status:blocked- Blocked by dependenciesstatus:needs-discussion- Needs team discussionstatus:implementation-pending- Approved, waiting for implementationstatus:draft- Draft/work in progressobsolete- No longer relevant
Milestone Tags
milestone:b1-foundation- B1 milestonemilestone:b2-features- B2 milestonemilestone:b3-integration- B3 milestone
Special Tags
epic- Epic tracking issueoctave-integration- OCTAVE integration work
Usage Pattern
Before creating a GitHub issue:
# 1. Verify current labels (labels can change over time)
gh label list --json name --jq '.[].name'
# 2. Create issue with ONLY valid labels
gh issue create \
--title "Issue Title" \
--label "enhancement,priority:p2-medium,phase:b1" \
--body "Issue description"
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 · 130 lines · 21 tokens per session scan A aa9b3a2ee0cb
github-labels is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,000 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-09-03.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.