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.
git clone --depth 1 https://github.com/LaStrada/claudeWrote 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/plugins/lastrada/claude/pr-tasklist)<a href="https://agentmods.dev/plugins/lastrada/claude/pr-tasklist"><img src="https://agentmods.dev/badge/plugins/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.
<a href="https://agentmods.dev/plugins/lastrada/claude/pr-tasklist"><img src="https://agentmods.dev/badge/plugins/lastrada/claude/pr-tasklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pr-tasklist 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 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.
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.
What it actually says
{
"name": "pr-tasklist",
"description": "GitHub PR dashboard for Claude Code. Shows PRs you authored, are assigned to, are review-requested on, plus a personal followed list. Live data via the official GitHub MCP server (preferred) or `gh api graphql` (fallback); auto-detects whichever is available and falls back on failure. Followed list backed by either local JSON (single machine, safest for private/internal work) or a secret GitHub Gist (best-effort multi-machine sync, suitable for public OSS). First-run setup prompts the user to pick storage with an explicit privacy warning. Interactive numbered tables with an action loop — open-in-browser, follow, unfollow, and a view-toggle panel — that repeats until you're done. Needs either `gh` CLI or a GitHub MCP server.",
"version": "0.2.0",
"author": {
"name": "Ståle Storø Hauknes",
"url": "https://github.com/LaStrada"
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 200 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 10 lines scan A 718af075d835
pr-tasklist is a plugin published in the GitHub repository LaStrada/claude (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.
Other plugins, from other repositories
git-sidebar
A lazygit-style side pane: every worktree of the repository and its local branches as rows you click. A worktree row moves the session there with /cd; a branch row shows its last commits and offers switch (clean tree only) or open worktree. Docked floor to ceiling beside the transcript in the fullscreen layout, above…
git-pr
Committing, PR creation and review triage, and dependency upgrades.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested, stacked PR or MR with agents.