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 MithunWijayasiri/dotclaude --skill github-issue-creatorgit clone --depth 1 https://github.com/MithunWijayasiri/dotclaudeWrote 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/mithunwijayasiri/dotclaude/github-issue-creator)<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/github-issue-creator"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/github-issue-creator/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/mithunwijayasiri/dotclaude/github-issue-creator"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/github-issue-creator.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.00047 | $0.00808 |
| Opus 5.5 | $0.00019 | $0.00323 |
| Sonnet 5.5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
github-issue-creator 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Creator
Turn messy input into a clean issue, draft in chat, create with gh on approval.
Repo
Resolve from git remote get-url origin (repo name can differ from folder name). Never guess owner/repo.
Before any gh write: gh auth status; active account must match the one project instructions require.
Create flow
- Find templates:
.github/ISSUE_TEMPLATE/*(.ymlforms or.md). Readconfig.ymltoo (blank_issues_enabled: false→ must use a template). - Pick the template that fits. Several fit → ask.
- Missing required template fields (version, device, steps…) → ask all in one batch. Never guess. Unknown → write
Not provided. - Build body:
.ymlform → one### <field label>section per field, same order as the form.gh issue create --templatecannot fill forms, so mirror them. Include everyrequiredfield..mdtemplate →gh issue create --templateor copy its structure.- No template → fallback below.
- Labels:
gh label list --repo <repo>. Apply templatelabels:plus existing labels that clearly fit (e.g.accessibility). Never create labels. State which were applied. - Title: match style of
gh issue list --repo <repo> --limit 10. - Show draft (title, labels, body) in chat. Create only after user OK:
gh issue create --repo <repo> --title ... --label ... --body-file -(heredoc). - Reply with issue URL.
Fallback template (no repo template)
Drop sections with nothing to say.
## Summary
## Reproduction Steps
## Expected Behavior
## Actual Behavior
## Error Details
## Additional Context
Edit flow
Issue body may hold images or text the user added after creation. Rewriting from memory destroys them.
gh issue view <n> --repo <repo> --json title,body,labelsfirst, every time.- Edit only the parts requested. Keep everything else verbatim:
<img>,,user-attachmentsURLs, user's manual edits. - Labels untouched unless asked.
- Placeholder
<!-- drag the screenshot here -->→ remove once body has media; else leave. - Show what changed (before/after of edited parts) before
gh issue edit <n> --body-file -.
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.
- 3d ago First seen · 69 lines · 47 tokens per session scan A dc97785bb74b
github-issue-creator is a skill published in the GitHub repository MithunWijayasiri/dotclaude (4 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 808 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-10-26.
Other skills, from other repositories
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.