issues

issues is a skill for Claude Code, Codex from akka/ai-marketplace. It costs 23 tokens per session (1,045 once invoked), scanned A, original, Apache-2.0.

A workflow that turns an existing task list into ordered, actionable GitHub issues. GitHub issues are trackable work items, and dependency ordering puts prerequisite work first.

In plain words
What is it for?
Use it after creating a feature task list, when the project has a GitHub remote, to create issues for the listed tasks while checking for existing matches.
Why use it?
It reduces manual issue writing and helps prevent duplicate issues for tasks that already exist in the repository.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it after creating a feature task list, when the project has a GitHub remote, to create issues for the listed tasks while checking for existing matches.

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

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.

agentmods badge for issues

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

agentmods 80×15 button for issues

Your own site · 80×15
<a href="https://agentmods.dev/skills/akka/ai-marketplace/issues"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,045 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.00023 $0.01045
Opus 5 $0.00012 $0.00522
Sonnet 5 $0.00005 $0.00209
Haiku 4.5 $0.00002 $0.00104

Measured 10d ago against content hash defd22e64459, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 10d 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.

skills/issues/SKILL.md · 57 lines

How it starts

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

User Input

You MUST consider the user input before proceeding (if not empty).

Outline

  1. Locate the feature: Call the akka_sdd_list_specs MCP tool to find features. Verify that tasks.md exists for the target feature (has_tasks must be true). If tasks.md is missing, instruct the user to run /akka:tasks first. Read the tasks.md content from FEATURE_DIR.

  2. Build the task-ID set: Scan tasks.md for every task line — each starts with - [ ] followed by a task ID matching T and three digits (e.g. T001). Collect the set of task IDs you are about to process.

  3. Determine the GitHub repository from the git remote:

    git config --get remote.origin.url
    

    [!CAUTION] ONLY PROCEED TO THE NEXT STEPS IF THE REMOTE IS A GITHUB URL

  4. Fetch existing issues for deduplication: Before creating anything, use the GitHub MCP server's list_issues tool to find issues that already cover the task IDs from step 2.

    • Do not pass a state value — omitting it returns both open and closed issues.
    • Request perPage: 100 to minimize calls.
    • The tool uses cursor-based pagination: request further pages with the after parameter using the endCursor from the previous response.
    • For each issue title, match against the pattern \bT\d{3}\b (word boundaries so ST001 and T0010 do not false-match). This recognizes titles written as T001 ..., T001: ..., or [T001] .... When it matches one of your task IDs, mark that ID as already having an issue.
    • Stop paginating as soon as every task ID has been matched, or when there are no more pages. This bounds the number of calls on repos with large issue histories.
  5. Create issues for tasks that don't have one yet: For each task in tasks.md:

    • Strip the leading - [ ] and any [P] / [US#] markers to recover the task ID and description. Example: - [ ] T001 [P] [US1] Create User model in src/models/user.py → ID T001, description Create User model in src/models/user.py.
    • If the ID is in the "already has an issue" set from step 4: skip it and report T001 already has an issue, skipping.
    • Otherwise, use the GitHub MCP server's issue_write tool to create a new issue in the repository derived from the git remote. Use the canonical title format:

Read the full file on GitHub · 57 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. 10d ago First seen · 57 lines · 23 tokens per session scan A defd22e64459

Subscribe to this mod's changes

issues is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,045 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.