A setup procedure for preparing a GitHub repository for issue tracking. It synchronizes labels and creates or connects a GitHub Projects board, which organizes work items.

Use it to initialize labels and a Projects board for the current repository or another GitHub repository.

It removes the manual setup needed before a team can manage issues consistently in GitHub.

issue-setup — Skill for Claude Code by nirecom/agents

Install

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.

Any agent

npx skills add nirecom/agents --skill issue-setup

Clone the repo

git clone --depth 1 https://github.com/nirecom/agents

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nirecom/agents/issue-setup/github.svg)](https://agentmods.dev/skills/nirecom/agents/issue-setup)

Your own site

<a href="https://agentmods.dev/skills/nirecom/agents/issue-setup"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nirecom/agents/issue-setup"><img src="https://agentmods.dev/badge/skills/nirecom/agents/issue-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 454 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00027	$0.00454
Opus 5.5	$0.00011	$0.00182
Sonnet 5.5	$0.00005	$0.00091
Haiku 4.5	$0.00003	$0.00045

Measured 11d ago against content hash 89c87d8bedb8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/run-issue-setup.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/issue-setup/SKILL.md · 39 lines

What it actually says

Initialize a target repo for GitHub Issues: sync its label set and create/link a Projects v2 board.

Scope

Sync the target repo's label set (from agents/.github/labels.yml) and initialize its Projects v2 board.
Cross-repo aware: the target repo may differ from the CWD repo.
Non-GitHub remote: skip and notify the user.

Pre-flight

Read rules/github-issues.md — on-demand-only, never auto-injected; it owns the Labels section (sync-labels.sh, .github/labels.yml) and the Projects v2 project scope requirement.
AGENTS_MAIN_ROOT must be set.
gh must be authenticated with the project scope; if absent, tell the user to run gh auth refresh -s project and stop.
Run bin/is-github-dotcom-remote against the target repo; on rc=1, exit 0 with a notice.

Procedure

IS-1. Confirm the target repo via AskUserQuestion:

current: use the CWD repo (resolve via gh repo view).
other: prompt for an OWNER/REPO string.

IS-2. Sync labels (no confirmation — automatic): run run-issue-setup.sh --step labels --repo "$TARGET_REPO".

IS-3. Check the project: run run-issue-setup.sh --step check-project --repo "$TARGET_REPO" → rc=0 present / rc=1 absent.

IS-4. When the project is absent, AskUserQuestion:

create: run run-issue-setup.sh --step ensure-project --repo "$TARGET_REPO".
skip: notify the user that a manual link is required, then exit 0.

IS-5. Report the outcome to the user.

Backend script path: $AGENTS_MAIN_ROOT/skills/issue-setup/scripts/run-issue-setup.sh.

Files

What ships with it

1 file 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.

scripts/run-issue-setup.sh 3.4 KB runs code

Changes

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 Changed 89c87d8bedb8
1mo ago First seen · 39 lines · 27 tokens per session scan A 4b3b93b14bdf

Subscribe to this mod's changes

issue-setup is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 454 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-08-31.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens