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 agentmods add skills/technicalpickles/pickled-claude-plugins/inboxnpx 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00025 | $0.00545 |
| Opus 5 | $0.00013 | $0.00272 |
| Sonnet 5 | $0.00005 | $0.00109 |
| 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 3d 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.
- 3d 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 (10 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 545 once invoked, about $0.0001 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-31.
Other skills, from other repositories
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
n8n:reproduce-bug
Reproduce a bug from a Linear ticket with a failing test. Expects the full ticket context (title, description, comments) to be provided as input.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.