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 kBashar/myagentskills --skill ghissuegit clone --depth 1 https://github.com/kBashar/myagentskillsWrote 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/kbashar/myagentskills/ghissue)<a href="https://agentmods.dev/skills/kbashar/myagentskills/ghissue"><img src="https://agentmods.dev/badge/skills/kbashar/myagentskills/ghissue/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/kbashar/myagentskills/ghissue"><img src="https://agentmods.dev/badge/skills/kbashar/myagentskills/ghissue.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.00045 | $0.03254 |
| Opus 5.5 | $0.00018 | $0.01302 |
| Sonnet 5.5 | $0.00009 | $0.00651 |
| Haiku 4.5 | $0.00005 | $0.00325 |
Grade A, and why
ghissue 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghissue
Overview
File a GitHub issue whose body is written for humans first. Someone who does not contribute to the codebase — a PM, a designer, a new joiner — must be able to scan it in about fifteen seconds and come away with the intent, the goal, and the impact. An implementer must come away with a clear direction and a definition of done.
Core principle: brief, simple, comprehensive. Brevity is a budget you spend deliberately, not a licence to omit what the reader needs.
Workflow
Create one todo per step.
Step 1 — Preflight (automated)
scripts/preflight.sh [repo-hint]
Pass a repo hint whenever the request names one ("open this in the web frontend"). Branch on the exit code:
| Exit | Meaning | Do |
|---|---|---|
| 0 | Ready. Prints REPO=owner/name then the repo's labels |
Continue; keep both |
| 2 | gh missing or unauthenticated |
Draft-only mode (below). Do not stop |
| 3 | No target repo resolvable | Stop. Ask which repo, then re-run |
| 4 | Hint matched several repos | Ask the user to pick from CANDIDATES: |
Draft-only mode: run steps 2–4 and 5, write the body to a file, print it, and hand over the path so the user can paste it into GitHub. Skip labels. A missing gh costs you the filing, not the issue.
Step 2 — Classify: bug or not
This decides one thing only: whether ## Steps to reproduce exists. Ask when genuinely unclear. Do not infer a bug from the words "broken", "slow", or "doesn't work" — a request to add filtering is a feature even when the complaint sounds like a fault.
Step 3 — Quick scan, then ask
Read the relevant code so present state is fact, not recollection. Timebox it.
When something material is still unknown after the scan — ask the user now. Unknowns belong in the conversation, not in the issue. An open question written into the body is a question every future reader has to re-answer.
That includes every example value headed for the API changes table, and what "done" means when the request does not make it clear. Ask here; do not derive them while drafting and disclose the derivation later.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 229 lines · 45 tokens per session scan A ab18568d2440
ghissue is a skill published in the GitHub repository kBashar/myagentskills (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 3,254 once invoked, about $0.0002 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
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…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
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.
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.
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)…
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…