Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add artem-from-ua/claude-plugins/plugin install issue-conventionsWrote 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/artem-from-ua/claude-plugins/issue-conventions-relabel)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/issue-conventions-relabel"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/issue-conventions-relabel/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/artem-from-ua/claude-plugins/issue-conventions-relabel"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/issue-conventions-relabel.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.00088 | $0.01483 |
| Opus 5.5 | $0.00035 | $0.00593 |
| Sonnet 5.5 | $0.00018 | $0.00297 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
issue-conventions-relabel 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Conventions — Relabel
Classifies the existing backlog against the taxonomy and applies the result in reviewed batches.
Steps
1. Load the taxonomy
Resolve the config (.claude-plugin/ → .claude/ → ~/.claude/), take taxonomyDocument, and parse it: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/parse-taxonomy.py" <document>.
No config → point at /issue-conventions-setup and stop. This command never invents a taxonomy. A document that fails to parse → stop and show the reported line; there is no JSON fallback to fall back to.
2. Reconcile labels before touching issues
Run bash "${CLAUDE_PLUGIN_ROOT}/scripts/label-plan.sh" <document> --summary. If anything is missing on GitHub, the document was edited by hand and GitHub has not caught up — offer to create the missing labels in one confirmation.
Skipping this means gh issue edit --add-label fails on the first issue with a label that exists only in the document. Hand edits are legitimate by design, so this is an expected path, not an edge case.
3. Fetch the issues
bash "${CLAUDE_PLUGIN_ROOT}/scripts/fetch-issues.sh" writes the dump and prints its path. Comments are fetched lazily — only for issues the classifier flags with needsComments, via gh api repos/{owner}/{repo}/issues/N/comments, because --json comments returns empty for some issues.
Then, unless prEvidence.mode is off, run bash "${CLAUDE_PLUGIN_ROOT}/scripts/pr-evidence.sh" --mode <mode> --from-dump <dump>. It writes one JSON line per issue naming the merged PR that answered it and the files it changed; merge each line into its issue as prEvidence before classifying.
It costs two API calls per issue and buys what a title cannot: on the third polygon five labels were wrong because the title described a documentation symptom while the fix changed script logic. paths (the default) carries the files alone at roughly a third the size of full, which adds the PR's own words.
The mode is set during setup and lives in the config. Do not override it here — a run that quietly reads more than the maintainer agreed to is worse than a cheaper classification.
What ships with it
2 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.
- 1mo ago First seen · 83 lines · 88 tokens per session scan A f80ccef6468f
issue-conventions-relabel is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,483 once invoked, about $0.0004 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-08.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…