dev:auto:fetch-issue

dev:auto:fetch-issue is a skill for Claude Code from atournayre/claude-marketplace. It costs 26 tokens per session (1,232 once invoked), scanned A, original, MIT.

An automatic step that retrieves a GitHub issue, which is a tracked task or bug report, using its issue number. It reads the issue's title, description, labels, and status.

In plain words
What is it for?
Use it at the start of an automated feature workflow to load the task details from GitHub.
Why use it?
It avoids copying a feature specification by hand and checks that the issue number is valid and available in the current repository.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the dev plugin — 25 skills, 8 agents shipped together

Good fit Use it at the start of an automated feature workflow to load the task details from GitHub.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atournayre/claude-marketplace/auto-fetch-issue
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 atournayre/claude-marketplace --skill auto-fetch-issue
Clone the repo
git clone --depth 1 https://github.com/atournayre/claude-marketplace

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 25 skills, 8 agents.

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.

agentmods badge for dev:auto:fetch-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-fetch-issue/github.svg)](https://agentmods.dev/skills/atournayre/claude-marketplace/auto-fetch-issue)
Your own site
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-fetch-issue"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-fetch-issue/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.

agentmods 80×15 button for dev:auto:fetch-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-fetch-issue"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-fetch-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,232 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01232
Opus 5 $0.00013 $0.00616
Sonnet 5 $0.00005 $0.00246
Haiku 4.5 $0.00003 $0.00123

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

Security

Grade A, and why

dev:auto:fetch-issue 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 12d 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.

dev/skills/auto-fetch-issue/SKILL.md · 187 lines

How it starts

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

Objectif

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

Phase 0 (Initialisation) du workflow automatisé : récupérer la specification depuis une issue GitHub.

Exécuté au démarrage du workflow avant Phase 1.

Instructions

1. Valider le paramètre

  • Vérifier que l'argument est un numéro valide
  • Exit avec erreur si pas un numéro
issue_number=$ARGUMENTS

if ! [[ "$issue_number" =~ ^[0-9]+$ ]]; then
    echo "❌ Erreur : l'argument doit être un numéro d'issue GitHub"
    echo "Usage: /dev:auto:feature 123"
    exit 1
fi

2. Récupérer l'issue

Utiliser gh issue view pour récupérer le contenu :

issue_data=$(gh issue view "$issue_number" --json title,body,labels,state)
issue_exists=$?

if [ $issue_exists -ne 0 ]; then
    echo "❌ Issue #$issue_number non trouvée"
    echo "Vérifie que :"
    echo "  1. Le numéro est correct"
    echo "  2. Tu es authentifié sur GitHub (gh auth login)"
    echo "  3. L'issue existe dans le repo courant"
    exit 1
fi

3. Parser les données

Extraire les champs nécessaires :

# Utiliser jq pour parser
issue_title=$(echo "$issue_data" | jq -r '.title')
issue_body=$(echo "$issue_data" | jq -r '.body')
issue_state=$(echo "$issue_data" | jq -r '.state')
issue_labels=$(echo "$issue_data" | jq -r '.labels | map(.name) | join(", ")')

4. Valider l'issue

  • Vérifier que l'issue est en state "OPEN"
  • Vérifier que la description n'est pas vide
if [ "$issue_state" != "OPEN" ]; then
    echo "❌ Issue #$issue_number n'est pas ouverte (state: $issue_state)"
    exit 1
fi

if [ -z "$issue_body" ] || [ "$issue_body" == "null" ]; then
    echo "⚠️  Issue #$issue_number : description vide"
    echo "Ajoute une description détaillée avant de relancer le workflow"
    exit 1
fi

5. Afficher les infos

🔗 Issue GitHub récupérée

  #$issue_number : $issue_title
  État : $issue_state
  Labels : $issue_labels

  Description :
  ───────────────────────────────
  $issue_body
  ───────────────────────────────

Read the full file on GitHub · 187 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.

  1. 12d ago First seen · 187 lines · 26 tokens per session scan A d97c75ad4424

Subscribe to this mod's changes

dev:auto:fetch-issue is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 1,232 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

recipe-create-meet-space

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

googleworkspace/cli · 18 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

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

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

projects

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

me2resh/apexyard · 24 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