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 technicalpickles/pickled-claude-plugins --skill inboxgit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/inbox)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/inbox/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/technicalpickles/pickled-claude-plugins/inbox"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/inbox.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.00025 | $0.00553 |
| Opus 5.5 | $0.00010 | $0.00221 |
| Sonnet 5.5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
inbox 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 1mo 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
Git Inbox
Overview
Show PRs awaiting your review across repositories. Surfaces what needs your attention with context to prioritize.
Announce: "Using git:inbox to check PRs awaiting your review..."
When to Use
- Starting your day - "what needs my attention?"
- User asks about PRs to review
- User says "inbox", "review queue", "what's waiting on me?"
Workflow
1. Fetch PRs Awaiting Review
# PRs where you're requested reviewer
gh search prs --review-requested=@me --state=open --json repository,number,title,author,createdAt,url
# PRs where you're assigned
gh search prs --assignee=@me --state=open --json repository,number,title,author,createdAt,url
2. Enrich with Review Status
For each PR, get review state:
gh pr view {number} --repo {owner}/{repo} --json reviews,reviewRequests
3. Present Inbox
Format as actionable list:
## PRs Awaiting Your Review
### {repo} #{number}: {title}
- **Author:** @{author}
- **Age:** {days} days
- **URL:** {full_url}
- **Status:** {review_status}
---
{N} PRs need your attention. Check out a PR for local review?
Important:
- Always show full PR URL (clickable/copy-pasteable)
- Sort by age (oldest first) or priority
- Show review status (no reviews yet, changes requested, approved by others)
4. Offer Next Action
Use AskUserQuestion:
Which PR would you like to check out for review?
(A) #{number} - {title}
(B) #{number} - {title}
(C) #{number} - {title}
(D) None right now
If user picks one → invoke git:checkout with the PR.
Quick Reference
| Command | Purpose |
|---|---|
gh search prs --review-requested=@me --state=open |
PRs requesting your review |
gh pr view {n} --repo {r} --json reviews |
Get review status |
Related
git:checkout- Check out a PR for local reviewcode-review- Guide the actual review process (separate skill)
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.
- 1mo ago Changed · +1 lines f4110454be21
- 1mo ago First seen · 88 lines · 25 tokens per session scan A f07ca16cc332
inbox is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (12 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
review-pubsub-subscriptions
Reviews Dapr pub/sub subscriptions and handlers in .NET and Python (declarative, programmatic, streaming) for CloudEvent handling, response statuses, idempotency, dead-letter handling and duplicate subscriptions. Use for "review my Dapr subscribers" or "check pub/sub handlers for idempotency".
review-agent-tools
Reviews agent tool implementations for idempotency, input validation, docstring quality and conventions. Use for "review agent tools" or "check tool idempotency".
review-workflow-management
Read-only audit of the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) an app exposes for Dapr Workflows, with DWF-MGT-NNN findings. Use for "review workflow management" or "check workflow HTTP endpoints". To operate runs on Diagrid Catalyst use the catalyst-ai plugin.
review-pubsub-components
Reviews Dapr pub/sub configuration (components, Subscription files, resiliency, dapr.yaml and Aspire wiring) for inline secrets, unsecured brokers, dead-letter topics without retry policies, scopes and app-id or port collisions. Use for "review my pub/sub components" or "audit Dapr pubsub YAML".
review-pubsub-publishing
Reviews Dapr pub/sub publishing code in .NET and Python for swallowed publish failures, wrong pub/sub names, content types, client lifetime, bulk-publish partial failures and payload size. Use for "review my pub/sub publishing code" or "audit Dapr publish calls".
review-agent-orchestration
Reviews multi-agent orchestration for pub/sub topic conventions, loop safety and handoff correctness. Use for "review agent orchestration" or "check multi-agent handoffs".