open-issue

A workflow for filing GitHub issues in the agentdeck repository using a fixed structure: problem, proposed shape, notes, and completion criteria.

In plain words
What is it for?
Use it to write one concise issue, include reproduction details or API examples, check for duplicates, choose labels, and define observable conditions for completion.
Why use it?
It turns vague requests or bug reports into focused specifications that developers can implement and test.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/agentdecksdk/agentdeck/open-issue
Any agent
npx skills add agentdecksdk/agentdeck --skill open-issue
Clone the repo
git clone --depth 1 https://github.com/agentdecksdk/agentdeck

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 366 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00031 $0.00366
Opus 5 $0.00015 $0.00183
Sonnet 5 $0.00006 $0.00073
Haiku 4.5 $0.00003 $0.00037

Measured yesterday against content hash 4fd41816ad56, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

open-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 yesterday.

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.

.agents/skills/open-issue/SKILL.md · 34 lines

What it actually says

Open an agentdeck issue

Issues are implementation-ready specifications. Be concise, precise, and dense with signal.

Issue Structure

## Problem
What is broken or missing, and why it matters. For bugs: exact traceback and minimal reproduction steps.

## Proposed shape
The clean, user-intent API or behavior with minimal code snippets. Show the simplest path with zero leaked plumbing. Explicitly state what is out of scope.

## Notes
Constraints, affected modules, existing patterns to follow, related issues/PRs.

## Done when
Checklist of observable, testable behaviors (mapping 1:1 to deterministic tests without live model calls).

Rules

  • Anti-verbosity: Avoid fluff and rambling rationale. One clear sentence beats a paragraph.
  • Title: Terse and specific: <area>: <what> (e.g., runtime: propagate cancellation to subagents).
  • Single concern: One issue per topic; split unrelated asks.
  • Check duplicates: gh issue list --state open.
  • Labels: Select one type label (bug, enhancement, feature, chore, design, documentation, or finding) and the closest area:* label from gh label list.
  • Output limits: Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.
  • Create via gh issue create -t <title> -b <body> --label <type> --label <area> and verify the resulting issue has both labels before returning its URL.
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. yesterday First seen · 34 lines · 31 tokens per session scan A 4fd41816ad56

Subscribe to this mod's changes

open-issue is a skill published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 366 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.