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-setup)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/issue-conventions-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/issue-conventions-setup/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-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/issue-conventions-setup.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.00083 | $0.01934 |
| Opus 5.5 | $0.00033 | $0.00774 |
| Sonnet 5.5 | $0.00017 | $0.00387 |
| Haiku 4.5 | $0.00008 | $0.00193 |
Grade A, and why
issue-conventions-setup 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Conventions — Setup
Designs a taxonomy for this repository, writes it as a document, and creates the labels.
Steps
1. Preflight
Run gh auth status — stop with instructions if it fails. Get the repo with gh repo view --json nameWithOwner.
Count issues: bash "${CLAUDE_PLUGIN_ROOT}/scripts/fetch-issues.sh" --count-only. If the count is below thresholds.minIssues (30 by default), use AskUserQuestion: Continue anyway (the taxonomy will lean on code structure, with weaker evidence for topical axes) or Postpone. This is a recommendation, never a block — with fewer issues there is not enough material to see what the maintainers actually work on.
If a config already exists, read it and its document, and pre-fill every answer from the document.
2. Scan the repo for candidates
Follow ${SKILL_DIR}/references/repo-scan.md. It produces four lists: structural candidates with a proposed axis name, topical candidates each backed by two real issue numbers, title prefixes already in use, and the existing labels with their usage counts.
3. Interview
Run it per ${SKILL_DIR}/references/interview.md — the full question order, option texts, and defaults live there. Every question offers the step-2 candidates; never an empty prompt.
Anything shown as a candidate but not chosen goes into ignore=, alongside what step 2 filtered out automatically. Without this the drift check keeps re-raising what the user already declined.
4. Look for gaps before confirming
Before showing the axis table, run one cheap pass: which issues do not fit the dictionary just assembled? Sample 20–30 across the corpus and ask, per issue, whether any value covers it.
The frequency scan in step 2 cannot find these by construction — it keeps terms recurring in three or more issues, so a surface with one or two loses out. On the second polygon four values had to be added mid-run this way, each covering 1–4 issues, and each addition meant returning to already-classified batches. Finding them here costs one pass; finding them later costs a re-run.
What ships with it
4 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 · 97 lines · 83 tokens per session scan A 75c8016acb7b
issue-conventions-setup is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 1,934 once invoked, about $0.0003 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…