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 agentmods add commands/skyfox675/agents-skills/gh-issuegit clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/commands/skyfox675/agents-skills/gh-issue)<a href="https://agentmods.dev/commands/skyfox675/agents-skills/gh-issue"><img src="https://agentmods.dev/badge/commands/skyfox675/agents-skills/gh-issue.svg" alt="Measured on agentmods" 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.00074 | $0.00947 |
| Opus 5 | $0.00037 | $0.00474 |
| Sonnet 5 | $0.00015 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
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 6d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gh-issue — file a groomed GitHub issue
Arguments: $ARGUMENTS
Parse them as:
- The first token (or quoted phrase) is the breadcrumb — a UI path (
Settings > Billing > Invoice row), a route (/dashboard), a component or object name, or a file path. - Optional
model:<tier>andeffort:<level>tokens may appear anywhere in the arguments. Strip them out before reading the rest. Valid tiers/levels come from the gh-issue-labels skill's taxonomy (model:sonnet|opus|fable; effort:low|medium|high|max, adjusted to the project's bound model lineup). An unrecognized value is a typo — warn the operator and file without that label rather than inventing one. - Everything else is the description of the problem as the operator experienced it.
Example: /gh-issue "Settings > Billing > Invoice row" clicking an invoice opens a 404 model:opus effort:high
The gh-issue-filing skill is the protocol — issue anatomy, labels, duplicate etiquette all come from it. This command is the entry point; consult the skill before drafting. (Tracking work in Jira instead? Use /jira-issue.)
Steps
-
Recon the breadcrumb. Resolve it to real code: search the repo for the component/route/object it names and capture the concrete
file:linepointers the skill's evidence section requires. Verify every pointer by reading it before citing — stale references are worse than none. If the breadcrumb matches multiple candidates, cite the strongest and list the runners-up in the issue body so the implementer doesn't re-derive them. -
Check for duplicates per the skill's etiquette: search open issues for the key terms from the breadcrumb and description. If a live duplicate exists, enrich it with a comment (your recon evidence) instead of forking a new issue, and report that outcome instead. If the operator passed
model:/effort:, apply those labels to the duplicate — that instruction stands regardless of which issue carries the work. -
Draft the issue using the skill's groomed anatomy: title per the project's convention, Symptom (from the operator's description, verbatim where possible), verified
file:lineevidence (from step 1), Desired behavior, independently-testable Acceptance criteria, and the traceability hint if the project binds one. Infer priority from user impact and state the reasoning in one line of the body — do not stop to ask. Write the Symptom and Desired-behavior prose naturally and run the body through thehumanizerskill before filing — the issue is a story a human reads; keep the verifiedfile:lineevidence and the acceptance-criteria checklist exactly as captured.
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.
- 6d ago First seen · 34 lines · 74 tokens per session scan A 721e1d535fcb
gh-issue is a command published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 947 once invoked, about $0.0004 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.