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 tonyghiani/ai-essentials --skill gh-issue-writergit clone --depth 1 https://github.com/tonyghiani/ai-essentialsWrote 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/tonyghiani/ai-essentials/gh-issue-writer)<a href="https://agentmods.dev/skills/tonyghiani/ai-essentials/gh-issue-writer"><img src="https://agentmods.dev/badge/skills/tonyghiani/ai-essentials/gh-issue-writer/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/tonyghiani/ai-essentials/gh-issue-writer"><img src="https://agentmods.dev/badge/skills/tonyghiani/ai-essentials/gh-issue-writer.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.00064 | $0.00528 |
| Opus 5 | $0.00032 | $0.00264 |
| Sonnet 5 | $0.00013 | $0.00106 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
gh-issue-writer 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 10d 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
GitHub Issue Writer
Generate GitHub issue content in this preferred template. Output only the
formatted Markdown — never call gh issue create.
Workflow
- Read the user's brief (feature request, bug report, or context).
- If the brief is too vague to produce concrete acceptance criteria, ask one round of clarifying questions before drafting.
- Produce the issue using the exact template below.
- Present the result in two parts:
- Title (plain text, one line) — for the GitHub title field
- Body (fenced Markdown block) — for the issue description
Template
Title (plain text, not a heading in the body):
[Area] Action-oriented and concise description
Body:
## 📓 Summary
[1-2 sentences: what is happening, why it matters, user impact.]
## ✔️ Acceptance criteria
* [Specific, measurable outcome 1]
* [Specific, measurable outcome 2]
* [Edge cases or UI/UX states if applicable]
## 💡 Implementation hints
* [Components or layers to touch — UI, API, state, tests]
* [Data model considerations — types, schemas, migrations]
* [Compact bullet points; no actual code]
Writing Rules
- Title:
[Area]prefix, then an action-oriented phrase (e.g.,[Auth] Support password reset via email link). - Summary: 1-2 sentences. Describe observable behavior, why it matters, and user impact. No filler.
- Acceptance criteria: Each bullet is a specific, testable outcome. Include edge cases and relevant UI states.
- Implementation hints: High-level pointers only. Mention files, components, or schemas by name in
inline code. Never write actual implementation code. - Tone: Professional, clear, neutral, highly technical. Focus on observable behavior.
- Formatting: Bold for key concepts.
Inline codefor technical terms, field names, file names. Concrete examples in (parentheses) when helpful. - Keep the body concise — aim for ≤30 lines of Markdown.
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.
- 10d ago First seen · 54 lines · 64 tokens per session scan A 267dfd236072
gh-issue-writer is a skill published in the GitHub repository tonyghiani/ai-essentials (7 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 528 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…