Gas Town is a workspace manager for coordinating multiple AI coding agents across projects while preserving their work state in git-backed records. Developers use it to organize agents, tasks, identities, mailboxes, and handoffs across repositories. Its catalogue add-ons support operating and coordinating Gas Town workflows.
Borrowing it
Nothing to install: this file belongs to gastownhall/gastown. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gastownhall/gastown/main/.claude/skills/ghi-list/SKILL.mdgit clone --depth 1 https://github.com/gastownhall/gastownWrote 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/gastownhall/gastown/ghi-list)<a href="https://agentmods.dev/skills/gastownhall/gastown/ghi-list"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/ghi-list/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/gastownhall/gastown/ghi-list"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/ghi-list.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00642 |
| Opus 5 | $0.00017 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
ghi-list 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GHI List - Formatted GitHub Issues Table
Display GitHub issues in a clean ASCII box-drawing table format.
Usage
/ghi-list [options]
Options (passed to gh issue list)
--state open|closed|all- Filter by state (default: open)--assignee <user>- Filter by assignee--label <label>- Filter by label (can repeat)--limit <n>- Max items to fetch (default: 30)--author <user>- Filter by author--milestone <name>- Filter by milestone
Execution Steps
- Run
gh issue listwith any provided options plus--json number,assignees,labels,title,state - Format output as an ASCII table using box-drawing characters
- Truncate titles to fit reasonable terminal width (~45 chars)
- Show first assignee only, or "-" if none
- Show first 2-3 labels abbreviated, or "-" if none
Output Format
Use this exact table style with box-drawing characters:
┌───────┬────────────┬─────────────────┬───────────────────────────────────────────────┬────────┐
│ Issue │ Assignee │ Labels │ Title │ State │
├───────┼────────────┼─────────────────┼───────────────────────────────────────────────┼────────┤
│ 372 │ max │ enhancement │ Create /pr-list and /ghi-list skills │ OPEN │
│ 371 │ - │ bug, priority │ Fix null pointer in auth module │ OPEN │
│ 370 │ joe │ - │ Update documentation for new API │ CLOSED │
└───────┴────────────┴─────────────────┴───────────────────────────────────────────────┴────────┘
Table Requirements
- Use Unicode box-drawing:
┌ ┐ └ ┘ ├ ┤ ┬ ┴ ┼ │ ─ - Right-align issue numbers
- Left-align text columns
- Pad columns consistently
- For assignees: show login of first assignee, "-" if none
- For labels: show comma-separated names (truncate if >17 chars)
- Show count summary below table: "N issues (M open, K closed)"
Example Commands
# Default - open issues
gh issue list --json number,assignees,labels,title,state
# With filters
gh issue list --state all --label bug --json number,assignees,labels,title,state
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.
- 12d ago First seen · 71 lines · 35 tokens per session scan A a47147dcfcb9
ghi-list is a skill published in the GitHub repository gastownhall/gastown (18,000 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 642 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.