agentmods.dev

pr-tasklist

pr-tasklist is a skill for Claude Code from LaStrada/claude. It costs 173 tokens per session (6,636 once invoked), scanned C, original, MIT.

A read-only dashboard for GitHub pull requests, which are proposed code changes awaiting review or merging. It groups relevant pull requests into authored, assigned, review-requested, and followed sections.

In plain words
What is it for?
Use it to see your open pull requests, assigned work, requested reviews, and personally followed pull requests.
Why use it?
It gathers pull requests from across repositories so developers do not have to check each repository separately.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Part of the pr-tasklist plugin — 1 skill, 1 command shipped together

not rated 2repo 4mo ago C scan 173 tokens original MIT

Good fit Use it to see your open pull requests, assigned work, requested reviews, and personally followed pull requests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lastrada/claude/pr-tasklist
View source ↗ LaStrada/claude
Install

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.

Any agent
npx skills add LaStrada/claude --skill pr-tasklist
Clone the repo
git clone --depth 1 https://github.com/LaStrada/claude

Made for: Claude Code.

Or install pr-tasklist, the plugin that ships this one along with the rest of its 1 skill, 1 command.

Wrote 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.

agentmods badge for pr-tasklist

README.md
[![agentmods](https://agentmods.dev/badge/skills/lastrada/claude/pr-tasklist/github.svg)](https://agentmods.dev/skills/lastrada/claude/pr-tasklist)
Your own site
<a href="https://agentmods.dev/skills/lastrada/claude/pr-tasklist"><img src="https://agentmods.dev/badge/skills/lastrada/claude/pr-tasklist/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.

agentmods 80×15 button for pr-tasklist

Your own site · 80×15
<a href="https://agentmods.dev/skills/lastrada/claude/pr-tasklist"><img src="https://agentmods.dev/badge/skills/lastrada/claude/pr-tasklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 173 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,636 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00173 $0.06636
Opus 5.5 $0.00069 $0.02654
Sonnet 5.5 $0.00035 $0.01327
Haiku 4.5 $0.00017 $0.00664

Measured 2mo ago against content hash a63c7d01f48c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

pr-tasklist scanned grade C 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

trap 'rm -rf "$tmpdir"' EXIT
plugins/pr-tasklist/skills/pr-tasklist/SKILL.md · 495 lines

How it starts

The opening of the file, as written. The whole thing — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pr-tasklist

A cross-repo dashboard for the PRs the user cares about. Lives in four sections:

  1. Mine — PRs the user authored.
  2. Assigned — PRs the user is assigned to.
  3. Review-requested — PRs where the user is a requested reviewer.
  4. Followed — user-curated list, persisted in a storage backend.

The first three are live reads via the GitHub MCP server (preferred) or gh api graphql (fallback). The fourth requires a storage backend (local JSON or secret Gist), set up on first run.

When this applies

Trigger phrases (not exhaustive):

  • "show my PRs" / "my PR list" / "my open PRs" / "PR list"
  • "PR dashboard" / "PR queue" / "PR tasklist"
  • "what's on my plate" (in a dev context)
  • "what should I review" / "what PRs are waiting on me"
  • The user runs /prs (any subcommand: setup, reconfigure, unfollow, etc.).

Do NOT trigger for:

  • Reviewing a single PR (use code-review, review, or pr-review-toolkit:review-pr).
  • Creating a PR (use the standard PR-creation flow).
  • Managing issues, notifications, or discussions — out of scope.
  • Querying non-github.com hosts (Gitea, Forgejo, GitLab on prem, etc.) — gh only.

Hard constraints

  1. Read-only by default. Show the dashboard. Mutate state only on explicit user pick.
  2. Don't post comments, approve, request changes, or merge from this skill. Open-in-browser is the only outbound action.
  3. Confirm before any first-time gist creation. Never silently create a public artifact in the user's account.
  4. Show storage location whenever it changes. When following/unfollowing, end with a single line confirming where the state was persisted (path or gist URL).
  5. Never store API tokens. Rely entirely on gh CLI auth.
  6. Never hardcode usernames or orgs. This plugin is public; users come from any GitHub account.
  7. Surface auth/setup failures loudly. Don't paper over a missing gh auth status with an empty dashboard.

Steps

1. Detect backend + preflight

Read the full file on GitHub · 495 lines

Changes

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.

  1. 2mo ago First seen · 495 lines · 173 tokens per session scan C a63c7d01f48c

Subscribe to this mod's changes

pr-tasklist is a skill published in the GitHub repository LaStrada/claude (2 stars, last pushed 4mo ago), licensed MIT. It adds 173 tokens to every session and 6,636 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code reviewGit and workflow
Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

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.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

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…

umputun/revdiff · 248 tokens