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 aiya000/dotfiles --skill github-issue-creategit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/github-issue-create)<a href="https://agentmods.dev/skills/aiya000/dotfiles/github-issue-create"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/github-issue-create/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/aiya000/dotfiles/github-issue-create"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/github-issue-create.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 127 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00035 | $0.01214 |
| Opus 5.5 | $0.00014 | $0.00486 |
| Sonnet 5.5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
github-issue-create 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
github-issue-create
Create a GitHub issue using gh issue create with an auto-generated title and description.
Behavior
-
Check git/gh user consistency:
- Run
git config user.nameto get the local git identity - Run
gh auth statusto identify the active GitHub user - If
gh auth statusshowsX Failed to log in ... (keyring)for all accounts (even though the user has authenticated):- This is a known keyring issue in some environments — treat it as a keyring-unavailable environment
- Do NOT stop; proceed to the Keyring-unavailable fallback section below
- If they differ:
- If acting autonomously: run
gh auth switch --user "$(git config user.name)"- If switch succeeds: continue
- If switch fails: defer this skill. After all other work is done, report to the user: the git/gh user mismatch and that the switch failed
- If not acting autonomously: stop the skill and ask the user to resolve the mismatch before continuing
- If acting autonomously: run
- Run
-
Review the context provided by the user (bug description, feature request, task details, etc.)
-
Inspect the repository to understand context if needed:
git log --oneline -10— recent commits for contextgh issue list— existing issues to avoid duplicates
-
Scan for sensitive information before creating (see Secret Scan below)
-
Generate an appropriate title and description based on the issue type
-
Create the issue using
gh issue create
Issue Types and Labels
Select appropriate labels based on the issue type:
bug— Something isn't working correctlyenhancement— New feature or improvement requestdocumentation— Documentation improvementsquestion— Further information is requestedchore— Maintenance or internal tasks
Issue Description Format
The issue description should be written in English and follow this structure:
Bug Report
## Description
Brief description of the bug.
## Steps to Reproduce
1. Step one
2. Step two
3. Step three
## Expected Behavior
What should happen.
## Actual Behavior
What actually happens.
## Environment
- OS / version information if relevant
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.
- 1mo ago First seen · 147 lines · 35 tokens per session scan A e830b601fe96
github-issue-create is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,214 once invoked, about $0.0001 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-30.
Other skills, from other repositories
rescue__pull_request_conflict
An automated procedure for resolving merge conflicts in a pull request branch. A merge conflict happens when Git cannot combine competing changes by itself.
rescue__untracked_worktree
A guide for diagnosing missing files in Git worktrees. A Git worktree is another working directory connected to the same repository, often used for separate branches.
use-next-devtools
Reference for using the NextJS Dev Tools via the nextjs-agent. Use to debug or observe Next.js framework internals.
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.