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 skills/priyanshuchawda/tracepilot-gemini-cli/github-issue-creatornpx skills add priyanshuchawda/tracepilot-gemini-cli --skill github-issue-creatorgit clone --depth 1 https://github.com/priyanshuchawda/tracepilot-gemini-cliWrote 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/priyanshuchawda/tracepilot-gemini-cli/github-issue-creator)<a href="https://agentmods.dev/skills/priyanshuchawda/tracepilot-gemini-cli/github-issue-creator"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/github-issue-creator.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 | $0.00038 | $0.00698 |
| Opus 5 | $0.00019 | $0.00349 |
| Sonnet 5 | $0.00008 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 4d 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.
This is a copy
100% identical to github-issue-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Creator
This skill guides the creation of high-quality GitHub issues that adhere to the repository's standards and use the appropriate templates.
Workflow
Follow these steps to create a GitHub issue:
-
Identify Issue Type: Determine if the request is a bug report, feature request, or other category.
-
Locate Template: Search for issue templates in
.github/ISSUE_TEMPLATE/.bug_report.ymlfeature_request.ymlwebsite_issue.yml- If no relevant YAML template is found, look for
.mdtemplates in the same directory.
-
Read Template: Read the content of the identified template file to understand the required fields.
-
Draft Content: Draft the issue title and body/fields.
- If using a YAML template (form), prepare values for each
iddefined in the template. - If using a Markdown template, follow its structure exactly.
- Default Label: Always include the
🔒 maintainer onlylabel unless the user explicitly requests otherwise.
- If using a YAML template (form), prepare values for each
-
Create Issue: Use the
ghCLI to create the issue.- CRITICAL: To avoid shell escaping and formatting issues with multi-line Markdown or complex text, ALWAYS write the description/body to a temporary file first.
For Markdown Templates or Simple Body:
# 1. Write the drafted content to a temporary file # 2. Create the issue using the --body-file flag gh issue create --title "Succinct title" --body-file <temp_file_path> --label "🔒 maintainer only" # 3. Remove the temporary file rm <temp_file_path>For YAML Templates (Forms): While
gh issue createsupports--body-file, YAML forms usually expect key-value pairs via flags if you want to bypass the interactive prompt. However, the most reliable non-interactive way to ensure formatting is preserved for long text fields is to use the--bodyor--body-fileif the form has been converted to a standard body, OR to use the--fieldflags for YAML forms.
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.
- 4d ago First seen · 77 lines · 38 tokens per session scan A 298aa6043c40
github-issue-creator is a skill published in the GitHub repository priyanshuchawda/tracepilot-gemini-cli (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 698 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to github-issue-creator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
windows-encoding-fixes
Use when working with Windows (cmd/PowerShell console, MINGW64, script installation): stdout encoding (cp1251 vs UTF-8, UnicodeEncodeError on ✓/Cyrillic), CRLF/LF when writing files (md5 checks of mirrors), UTF-8 BOM for PowerShell 5.1, npm.cmd instead of npm, venv Scripts vs bin, PYTHONIOENCODING/PYTHONUTF8. Verified…
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
security-and-hardening
Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when personal data or privacy compliance (GDPR, CCPA) is involved.
spec-driven-development
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities.
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.