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/pr-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/pr-list)<a href="https://agentmods.dev/skills/gastownhall/gastown/pr-list"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/pr-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/pr-list"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/pr-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.00626 |
| Opus 5 | $0.00017 | $0.00313 |
| Sonnet 5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
pr-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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR List - Formatted Pull Request Table
Display GitHub pull requests in a clean ASCII box-drawing table format.
Usage
/pr-list [options]
Options (passed to gh pr list)
--state open|closed|merged|all- Filter by state (default: open)--author <user>- Filter by author--label <label>- Filter by label (can repeat)--limit <n>- Max items to fetch (default: 30)--assignee <user>- Filter by assignee--draft- Show only drafts--all-reviews- Include PRs with CHANGES_REQUESTED (excluded by default)
Execution Steps
- Run
gh pr listwith any provided options plus--json number,author,title,state,isDraft,reviewDecision - Filter out PRs with reviewDecision="CHANGES_REQUESTED" (unless
--all-reviewsspecified) - Format output as an ASCII table using box-drawing characters
- Truncate titles to fit reasonable terminal width (~50 chars)
- Truncate author names if needed (~18 chars)
- Show state as OPEN/CLOSED/MERGED/DRAFT, append "(changes requested)" if filtered with --all-reviews
Output Format
Use this exact table style with box-drawing characters:
┌─────┬────────────────────┬───────────────────────────────────────────────────┬────────┐
│ PR │ Author │ Title │ State │
├─────┼────────────────────┼───────────────────────────────────────────────────┼────────┤
│ 123 │ username │ feat: add new feature for something │ OPEN │
│ 122 │ another-user │ fix: resolve bug in component │ DRAFT │
└─────┴────────────────────┴───────────────────────────────────────────────────┴────────┘
Table Requirements
- Use Unicode box-drawing:
┌ ┐ └ ┘ ├ ┤ ┬ ┴ ┼ │ ─ - Right-align PR numbers
- Left-align text columns
- Pad columns consistently
- Show count summary below table: "N open PRs (M drafts)"
Example Commands
# Default - open PRs (excludes CHANGES_REQUESTED)
gh pr list --json number,author,title,state,isDraft,reviewDecision
# With filters
gh pr list --state all --author boshu2 --json number,author,title,state,isDraft,reviewDecision
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.
- 11d ago First seen · 70 lines · 35 tokens per session scan A 083bb25adc17
pr-list is a skill published in the GitHub repository gastownhall/gastown (18,000 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 626 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.