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/fmind/dotfiles/github-issuesnpx skills add fmind/dotfiles --skill github-issuesgit clone --depth 1 https://github.com/fmind/dotfilesWhat 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.00036 | $0.00614 |
| Opus 5 | $0.00018 | $0.00307 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
github-issues 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 yesterday.
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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage GitHub Issues
Use gh for evidence-backed issue operations. project-backlog owns local issue drafts; this skill owns confirmed remote issue state and authorized mutation.
Workflow
-
Confirm the target: Resolve the repository from the explicit URL or
git remote get-url origin, then stateOWNER/REPO. Never infer a different repository from a similarly named checkout. -
Refresh current state: Read the issue and relevant neighbors before proposing a change:
gh issue view <number> -R <owner>/<repo> --json number,title,body,state,stateReason,labels,assignees,milestone,comments,url gh issue list -R <owner>/<repo> --state all --search '<distinct terms>' --json number,title,state,url -
Deduplicate and preserve evidence: Prefer updating an existing issue when it represents the same outcome. Keep reproduction, acceptance criteria, dependencies, decisions, and proof; remove stale activity logs and duplicate checklists.
-
Check authority: Reading and drafting are safe defaults. Creation, edits, labels, assignments, comments, closure, reopening, locking, transfer, project changes, and deletion are separate remote mutations requiring user authority.
-
Apply one bounded mutation: Prepare substantial bodies in a temporary file and pass it with
--body-file; avoid shell interpolation and interactive prompts:gh issue create -R <owner>/<repo> --title '<title>' --body-file <body-file> gh issue edit <number> -R <owner>/<repo> --body-file <body-file> -
Verify from GitHub: Re-read the issue with
gh issue view --json ..., compare the intended fields, and report its URL. A successful command alone is not proof of final state.
Boundaries
- Do not close an issue merely because local code is green; verify the issue's acceptance criteria and requested delivery boundary.
- Do not assign people, notify them in comments, or alter projects and milestones without explicit coordination authority.
- Do not create issues from raw review findings until project-backlog has deduplicated and prioritized them.
- Use plan-execution for implementing an accepted issue and github-pull-request for the resulting PR.
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.
- yesterday First seen · 43 lines · 36 tokens per session scan A 7b7e55e5bb9b
github-issues is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 614 once invoked, about $0.0002 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
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…