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 mizukaizen/hive-doctrine-mcp --skill issue-labellinggit clone --depth 1 https://github.com/mizukaizen/hive-doctrine-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/mizukaizen/hive-doctrine-mcp/issue-labelling)<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/issue-labelling"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/issue-labelling/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/mizukaizen/hive-doctrine-mcp/issue-labelling"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/issue-labelling.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.00000 | $0.00634 |
| Opus 5 | $0.00000 | $0.00317 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
issue-labelling 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 11d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Issue Labelling
Use when new issues come in and need categorisation. Applies consistent labels for type, priority, and component to keep the issue tracker organised.
Trigger
Invoke this skill when processing new issues, during triage sessions, or when the /triage command runs.
Label Taxonomy
Type Labels (exactly one required)
| Label | Criteria |
|---|---|
bug |
Something that worked before is now broken, or documented behaviour does not match actual behaviour |
feature |
Request for new functionality that does not currently exist |
docs |
Documentation is missing, incorrect, or unclear |
question |
User needs help, not reporting a problem (redirect to discussions if available) |
Priority Labels (exactly one for bugs and features)
| Label | Criteria |
|---|---|
priority: critical |
Data loss, security vulnerability, or complete feature breakage with no workaround |
priority: high |
Significant functionality affected, workaround exists but is painful |
priority: medium |
Noticeable issue, reasonable workaround exists |
priority: low |
Minor inconvenience, cosmetic, or affects very few users |
Status Labels (applied as needed)
| Label | When to apply |
|---|---|
needs-info |
Cannot reproduce or understand without more detail from reporter |
confirmed |
Bug has been reproduced by a maintainer |
good first issue |
Well-scoped, clear solution path, minimal project knowledge required |
help wanted |
Maintainer cannot prioritise — community contributions welcome |
duplicate |
Already reported in another issue |
wontfix |
Intentional behaviour, or does not align with project direction |
Component Labels (project-specific)
Define component labels based on the project's architecture. Examples:
component: parsercomponent: clicomponent: apicomponent: ui
Decision Process
For each issue:
- Read the full issue including any reproduction steps or screenshots.
- Assign type — What category does this fall into?
- Check for duplicates — Search closed and open issues for similar reports.
- Assign priority — Based on impact and affected user count.
- Assign component — Which part of the project is affected?
- Check for first-issue suitability — Is the fix obvious, well-scoped, and achievable without deep project knowledge?
- Determine next action — Needs info? Ready to work on? Needs discussion?
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.
- 11d ago First seen · 64 lines · 0 tokens per session scan A 64e4a621f78a
issue-labelling is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 634 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-31.
Other skills, from other repositories
writbase-recipes
WritBase API recipes reference (internal).
extract-tasks
Review conversation and extract untracked work items as WritBase tasks (writbase:info, writbase:addtask). Use at end of session to capture untracked work.
loop
Poll WritBase for top tasks and work through them autonomously. Use when you want to process the task queue, auto-work, or run the work loop.
writbase-router
Route task, writbase, agent, permission, provenance, webhook, and delegation requests to WritBase MCP tools. Triggers on keywords like task, writbase, work, assign, delegate, permission, audit, webhook, subscribe, provenance, agent key.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…