Borrowing it
Nothing to install: this file belongs to agentdecksdk/agentdeck. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentdecksdk/agentdeck/dev/.claude/skills/open-issue/SKILL.mdgit clone --depth 1 https://github.com/agentdecksdk/agentdeckWrote 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.
[](https://agentmods.dev/skills/agentdecksdk/agentdeck/open-issue)<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/open-issue"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/open-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.
<a href="https://agentmods.dev/skills/agentdecksdk/agentdeck/open-issue"><img src="https://agentmods.dev/badge/skills/agentdecksdk/agentdeck/open-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00031 | $0.00438 |
| Opus 5.5 | $0.00012 | $0.00175 |
| Sonnet 5.5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 1mo 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.
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. For a feature, answer Q4 here (`docs/engineering/principles.md`): is this absorbing complexity, or transferring it to the user? That is the question we most often fail, and proposal time is when it is cheapest to fail it.
## Notes
Constraints, affected modules, existing patterns to follow, related issues/PRs.
## Pitfalls
Known failure modes, each backed by evidence.
## Must not
Explicit scope boundaries.
## 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, orfinding) and the closestarea:*label fromgh 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.
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.
- 1mo ago Changed c63c64c6c0b2
- 1mo ago Changed · +6 lines 6058d9504734
- 2mo ago First seen · 34 lines · 31 tokens per session scan A 4fd41816ad56
open-issue is a skill published in the GitHub repository agentdecksdk/agentdeck (4 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 438 once invoked, about $0.0001 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.
Other skills, from other repositories
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
project-access
Map, suggest and request the folder access a project needs: map (read-only report), suggest (draft .pi/access.json from this project's grants), provision (submit it for line-by-line operator approval). Use on "what folders can this project reach", "set up folder access", "write .pi/access.json", repeated folder access…
goga-task-by-specifying
Interactive task formulation from a raw request.
board
Use this when the person wants a kanban, to-do or status board: cards that move between named columns.
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…