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/dot/github-issuesnpx skills add fmind/dot --skill github-issuesgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/github-issues)<a href="https://agentmods.dev/skills/fmind/dot/github-issues"><img src="https://agentmods.dev/badge/skills/fmind/dot/github-issues.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.00041 | $0.00683 |
| Opus 5 | $0.00020 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Read and mutate GitHub issues with gh from verified remote state; project-backlog owns local issue drafts and prioritization.
Workflow
-
Confirm the target: resolve the repository from the explicit URL or
git remote get-url originand stateOWNER/REPO; never infer another repository from a similarly named checkout. -
Refresh current state 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: update the existing issue that represents the same outcome; keep reproduction, acceptance criteria, dependencies, decisions, and proof; drop stale logs and duplicate checklists.
-
Apply one bounded mutation the user authorized. Write substantial bodies to a temporary file and pass
--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 with
gh issue view --json ..., compare the intended fields, and report the URL; a zero exit code alone is not proof of final state.
Gotchas
- Green is not closed: verify the issue's acceptance criteria and requested delivery boundary before
gh issue close; local passing code is not delivery. - People and planning fields: assignments, comment notifications, milestones, and project changes are coordination acts; make them only when the request names them.
- Raw findings: route review findings through project-backlog before creating issues from them.
Official Skills
Upstream: cli/cli. List the current release, then install what the task needs at project scope after reviewing the snapshot (see agent-skills):
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 · 55 lines · 41 tokens per session scan A 75b2ebf75632
github-issues is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 683 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.