A skill for checking GitHub issues for the current code repository. It can list open or closed issues, show a particular issue, filter by label, and search by keyword.

Reviewing open tickets, inspecting issue details, filtering issues such as bugs or enhancements, and searching the repository's issue list.

It saves you from manually navigating GitHub when you need a quick view of the repository's bug reports, requests, or backlog.

issues — Skill for Claude Code and Codex by Magnus-Gille

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 Magnus-Gille/claude-skills --skill issues

Clone the repo

git clone --depth 1 https://github.com/Magnus-Gille/claude-skills

Made for: Claude Code, Codex.

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/magnus-gille/claude-skills/issues/github.svg)](https://agentmods.dev/skills/magnus-gille/claude-skills/issues)

Your own site

<a href="https://agentmods.dev/skills/magnus-gille/claude-skills/issues"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/issues/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/magnus-gille/claude-skills/issues"><img src="https://agentmods.dev/badge/skills/magnus-gille/claude-skills/issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 716 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.00036	$0.00716
Opus 5	$0.00018	$0.00358
Sonnet 5	$0.00007	$0.00143
Haiku 4.5	$0.00004	$0.00072

Measured 5d ago against content hash 7bb90850c5ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

issues 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 5d 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.

codex/issues/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Issues

Use this skill to inspect and summarize GitHub issues for the current repository.

Workflow

Detect the repository:
```
gh repo view --json nameWithOwner -q '.nameWithOwner'
```
If this fails, do not infer that the directory is not connected to GitHub. Check git remote get-url origin (or the relevant remote), resolve its owner/repo, and retry the read-only lookup. Retry gh api user --jq .login to distinguish an authentication/API problem from a missing or unusable remote; report the exact diagnosis before stopping.

Run the narrowest query that matches the request:

gh issue list --repo <owner/repo> --state open
gh issue view <number> --repo <owner/repo>
gh issue list --repo <owner/repo> --state open --label "<label>"
gh issue list --repo <owner/repo> --state closed --limit 10
gh issue list --repo <owner/repo> --state open --search "<query>"

Present results compactly.
- For issue lists, group by label and show #number - title.
- For one issue, show title, status, labels, body summary, comments/actions, and any referenced files.
- Mention Grimnir Roadmap board relevance when visible.
Prepare or publish a routed issue when requested.
- Resolve the owning repository and search it for likely duplicates before drafting.
- Prepare a title, verified labels only, and a temporary body file containing the problem, evidence, proposed fix, source, and owning-repository attribution. For cross-repo Grimnir work, add from:<sender> when the target uses sender labels and include Filed by: <sender> in the body.
- Preview the exact owner/repo, title, labels, body, and any board target. Use gh issue create --repo <owner/repo> --title ... --body-file <file> only after explicit user direction to publish. Preparation alone does not publish.
- Only the owning Grimnir session may add an item to the Grimnir Roadmap board, and only with explicit authorization for that board mutation. Report board relevance without adding it otherwise.

Read the full file on GitHub · 61 lines

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.

5d ago Changed · -28 lines · -6 tokens per session 7bb90850c5ab
12d ago First seen · 89 lines · 42 tokens per session scan A 7e07ce5d5e89

Subscribe to this mod's changes

issues is a skill published in the GitHub repository Magnus-Gille/claude-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 716 once invoked, about $0.0002 per session on Opus 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

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

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

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

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens