agentmods.dev

strike: Skill for Claude Code

.claude/skills/issue-create-and-handle/SKILL.md

issue-create-and-handle is a skill for Claude Code from jonathanung/strike. It costs 75 tokens per session (1,015 once invoked), scanned A, original, Apache-2.0.

A workflow for turning a reported problem or requested change into one approved GitHub issue and immediately assigning it for implementation. It checks the repository, existing issues, pull requests, and required access before creating anything.

In plain words
What is it for?
Use it to inspect the codebase, search for duplicates, draft an issue with scheduling headers, get approval, create and assign it, and hand it to the issue-handler.
Why use it?
It prevents duplicate or poorly scoped issues and ensures the issue includes the behavior, acceptance criteria, and test expectations needed for implementation. The issue must be approved before creation.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions AGENTS.md.

This is jonathanung/strike's own configuration. It tells Claude Code how to work on strike itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything strike configures →

not rated 5repo today A scan 75 tokens original Apache-2.0
View source ↗ jonathanung/strike strike.jonathanung.ca
Reuse

Borrowing it

Nothing to install: this file belongs to jonathanung/strike. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jonathanung/strike/main/.claude/skills/issue-create-and-handle/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jonathanung/strike

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.

agentmods badge for issue-create-and-handle

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathanung/strike/issue-create-and-handle/github.svg)](https://agentmods.dev/skills/jonathanung/strike/issue-create-and-handle)
Your own site
<a href="https://agentmods.dev/skills/jonathanung/strike/issue-create-and-handle"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-create-and-handle/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 issue-create-and-handle

Your own site · 80×15
<a href="https://agentmods.dev/skills/jonathanung/strike/issue-create-and-handle"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-create-and-handle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,015 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.00075 $0.01015
Opus 5.5 $0.00030 $0.00406
Sonnet 5.5 $0.00015 $0.00203
Haiku 4.5 $0.00007 $0.00102

Measured 2mo ago against content hash 61cabbb8b9e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

issue-create-and-handle 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 2mo 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.

.claude/skills/issue-create-and-handle/SKILL.md · 100 lines

How it starts

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

Create, approve, assign, and handle an issue

Convert the user's request into one scoped GitHub issue. The issue body must be approved before it is created. Once created, assign it to the authenticated GitHub user and immediately invoke issue-handler for that issue.

Preconditions

  • gh auth status succeeds.
  • The current directory is a Git repository with a GitHub remote.
  • The user has described a problem, change, or outcome.

Stop and ask if authentication, repository access, or the required GitHub permissions are unavailable.

Workflow

  1. Inspect

    • Read AGENTS.md and relevant code, tests, and configuration.
    • Search existing open issues and PRs for duplicates: 
      gh issue list --state open --limit 100 --search "<key terms> in:title,body"
gh pr list --state open --search "<key terms>"
    • If an existing issue or PR already covers the request, report it and stop. Do not create a duplicate.

  2. Draft

    • State the observed or requested behavior, likely affected area, acceptance criteria, and test expectations.
    • Headers are required on every new issue (orchestrator depends on them): 
      wave: 0
depends: none
blocks: none
conflicts: none
priority: bugs-first
    • Use a concise draft with this body structure: 
      wave: 0
depends: none
blocks: none
conflicts: none
priority: bugs-first

## Problem
...

## Scope
...

## Acceptance criteria
- ...

## Verification
- Tier: A | B | C
- ...
    • For a feature rather than a bug, use an appropriate wave and priority: feature.
    • Set depends / conflicts / blocks from repository evidence:
      • conflicts when the change likely touches the same hotspots as another open issue (keymap/defaults, engine/turn.go, tool registry/defer, shared protocol events) — list those issue numbers.
      • depends when another issue must land first.
    • Do not create feature issues with missing headers; refuse and re-draft.

Read the full file on GitHub · 100 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. 2mo ago First seen · 100 lines · 75 tokens per session scan A 61cabbb8b9e5

Subscribe to this mod's changes

issue-create-and-handle is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 1,015 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-08-31.

Git and workflowProject management
Related

Other skills, from other repositories

antfu-issue-triage

Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…

antfu/skills · 76 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…

vybestack/llxprt-code · 88 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens