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 show-issues-overviewgit 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/show-issues-overview)<a href="https://agentmods.dev/skills/aiya000/dotfiles/show-issues-overview"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/show-issues-overview/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/show-issues-overview"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/show-issues-overview.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.00069 | $0.04259 |
| Opus 5.5 | $0.00028 | $0.01704 |
| Sonnet 5.5 | $0.00014 | $0.00852 |
| Haiku 4.5 | $0.00007 | $0.00426 |
Grade A, and why
show-issues-overview scanned grade A with 1 finding 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 24d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`glab` is **not necessarily installed**. If `glab` is missing, do not improvise with `curl` and a How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
show-issues-overview
Description
Print an overview table of the issues of the project the current directory belongs to.
This is a read-only briefing. It exists so the user can look at everything that is open in one glance and pick what to do next -- so the output is one table, short enough to read without scrolling, not a dump of every field the forge knows.
The issue source depends on what kind of project this is:
| Project hosting | Source of issues |
|---|---|
| GitHub | GitHub Issues of the remote repository |
| GitLab | GitLab Issues of the remote repository |
| Neither | TODO.md or a similarly named file in the repository |
Arguments
All optional, and more than one may be given at once (list all, table 10, list bug). Pass
them through to the forge CLI where they map naturally.
Which issues to show:
<none>-- open issues, up to 50all-- include closed issues as wellclosed-- closed issues only<number>-- use that as the maximum number of issues to list, instead of 50- anything else -- treat it as a label / keyword filter, and say in the output that the list is filtered
How to print them:
table, or no format word at all -- Output format: tablelist-- Output format: list
table and list are format words. Consume them as the output shape and never pass them on as a
label or keyword filter, even though the fallback rule above would otherwise swallow them. An issue
genuinely labelled list is still reachable with an explicit --label list, and that collision is
rare enough to be worth the plain argument.
Step 1: Decide what kind of project this is
- Locate the project root with
git rev-parse --show-toplevel- If this fails, the directory is not a git repository -- go straight to Step 4 (no forge)
- List remotes with
git remote -v- Prefer the
originremote; if there is noorigin, use the first remote listed - If there is no remote at all, go to Step 4 (no forge)
- Prefer the
- Read the host out of the remote URL (both
https://host/owner/repo.gitandgit@host:owner/repo.gitforms)- host is
github.com, or starts withgithub.-- Step 2 (GitHub) - host is
gitlab.com, or containsgitlab-- Step 3 (GitLab) - any other host -- it may still be a self-hosted GitHub Enterprise or GitLab instance.
Run
gh repo view --json name 2>&1once; if it succeeds, treat it as GitHub. Otherwise runglab repo view 2>&1once; if it succeeds, treat it as GitLab. If both fail, go to Step 4 (no forge)
- host is
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.
- 24d ago First seen · 323 lines · 69 tokens per session scan A a75d758ee570
show-issues-overview is a skill published in the GitHub repository aiya000/dotfiles (21 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 4,259 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-22.
Other skills, from other repositories
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
autopilot-triage
Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.
create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
write-ticket-description
Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation and for every rewrite of an existing issue's body — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without…
implement-unattended
Take a ticket whose approach and design are already approved through implementation, review and evidence to a draft PR, with nobody watching. Escalates decisions on the ticket and stops rather than choosing.
plan-unattended
Plan a ticket with nobody watching. Three independent discuss runs are reconciled into one approach and three design runs into one design, both are posted on the ticket, and implement-unattended is started in a new tmux window. Escalates on the ticket rather than taking a one-way decision.