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.
npx skills add mir-am/skills-agents-ai-coding --skill gh-issuegit clone --depth 1 https://github.com/mir-am/skills-agents-ai-codingWrote 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/mir-am/skills-agents-ai-coding/gh-issue)<a href="https://agentmods.dev/skills/mir-am/skills-agents-ai-coding/gh-issue"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-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/mir-am/skills-agents-ai-coding/gh-issue"><img src="https://agentmods.dev/badge/skills/mir-am/skills-agents-ai-coding/gh-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.00020 | $0.00738 |
| Opus 5 | $0.00010 | $0.00369 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
gh-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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
- Ask user if this is a bug or feature request (if not already stated)
- Draft a concise, AI-agent-readable title and body from session context
- Apply
bugorenhancementlabel (GitHub creates it if missing) - Create the issue via
gh issue createand return the URL
When to use me
Use this skill when:
- User discovers a bug or has a feature idea during a session
- User wants to log it as a GitHub issue without losing the session context
Prerequisites
- GitHub CLI (
gh) must be installed and authenticated - Must be inside a git repo with a GitHub remote
- If
ghnot installed → error: "Error: GitHub CLI not found. Install: https://cli.github.com/" - If no GitHub remote found → error: "Error: No GitHub remote found. Is this a GitHub repository?"
Workflow
-
Determine issue type
- If user did not specify → ask: "Is this a bug or a feature request?"
- Map to label: bug →
bug, feature request →enhancement
-
Draft the issue from session context
- Title: short, imperative, ≤60 chars
- Bug examples:
Fix null pointer in auth handler,Handle empty state in user list - Feature examples:
Add dark mode toggle to settings,Support CSV export for reports
- Bug examples:
- Body: use the 3-field format below
- Label:
bugorenhancement
- Title: short, imperative, ≤60 chars
-
Validate prerequisites
gh auth status git remote get-url origin -
Create the issue
gh issue create --title "<title>" --label "<bug|enhancement>" --body "<body>" -
Return the issue URL to the user
Issue Body Format
**Type:** Bug | Feature Request
**Context:** <1-2 sentences — what was happening in the session when this was found>
**Description:** <What needs to be done, written concisely for an AI agent to act on later>
Title Guidelines
- Imperative mood, present tense (e.g. "Fix", "Add", "Support", "Handle")
- ≤60 characters
- No period at end
- Specific enough for an AI agent to understand the scope without extra context
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.
- 8d ago First seen · 85 lines · 20 tokens per session scan A c8ab5e847a11
gh-issue is a skill published in the GitHub repository mir-am/skills-agents-ai-coding (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 738 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.
Other skills, from other repositories
skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-auto-improver, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
yak-worktree-workflow
Use when starting work on a yak - sets up an isolated git worktree, reads yak context, and guides the full cycle from claiming through merge and cleanup.
swe-worktree
Create an isolated git worktree for an SWE change workspace. Use before implementation when the user wants the change isolated from the current working tree.
git
Use when user asks for git operations: branch creation, committing changes, creating pull requests.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback.