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 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/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/fmind/dot/github-issues"><img src="https://agentmods.dev/badge/skills/fmind/dot/github-issues.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.00018 | $0.00756 |
| Opus 5.5 | $0.00007 | $0.00302 |
| Sonnet 5.5 | $0.00004 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
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 14d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Plan, read, and mutate GitHub issues from verified repository and remote state.
Workflow
Use gh for account selection, repository identity without printing raw remote URLs, bounded API calls, and request serialization when needed.
-
Confirm the target: resolve the repository from the explicit URL or
gh repo view --json nameWithOwner,visibilityand 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,url gh issue list -R <owner>/<repo> --state all --search '<distinct terms>' --limit 20 --json number,title,state,url -
Load discussion when relevant: fetch comments separately when decisions, acceptance criteria, or requested replies depend on them; preserve that context before editing. Narrow or paginate a search that reaches its limit before claiming no duplicate exists.
-
Deduplicate: update the existing issue that represents the same outcome; keep reproduction, acceptance criteria, dependencies, decisions, and proof; drop stale logs and duplicate checklists.
-
Draft before creating: for multiple findings or dependency-aware work, apply the backlog workflow and draft contract, present the reviewable set, and stop unless issue creation is already authorized.
-
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.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed f29e86afbec8
- 15d ago Changed · -4 lines · -2 tokens per session e31fd480e1e3
- 17d ago Changed · -6 lines 2d1088a20f2c
- 23d ago Changed · +1 lines d9e223f0c319
- 26d ago Changed ad78d815ac1d
- 1mo ago Changed · +3 lines · -30 tokens per session 6cb7e940aa18
- 1mo ago Changed · +1 lines bb072032df5c
- 1mo ago Changed · +1 lines · +9 tokens per session 53aa7f15681f
- 1mo ago Changed · +1 lines 3b75585a64f3
- 1mo ago First seen · 55 lines · 41 tokens per session scan A 75b2ebf75632
github-issues is a skill published in the GitHub repository fmind/dot (12 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 756 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-09-03.
Other skills, from other repositories
github-issues
Manage GitHub issues with gh: confirm repo and state, deduplicate, preserve evidence, and verify authorized creation, edits, labels, comments, or closure.
product-loop
Discovery, specification, launch, and learning for a product in one loop. Build-or-stop calls, MVP wedges, demand tests, customer interviews, PRDs, requirements, user journeys, acceptance, positioning, onboarding, rollout, pricing, pivots.
project-backlog
Turn audit findings into deduplicated, prioritized issue drafts with dependencies and explicit authorization before GitHub mutation.
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…
podio-ticket-updates
Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.