check-inbox

check-inbox is a skill for Claude Code from cookjohn/teammcp. It costs 29 tokens per session (479 once invoked), scanned A, original, MIT.

A procedure for checking unread TeamMCP inbox messages, sorting them by urgency and purpose, acknowledging each reviewed message, and summarizing what needs attention.

In plain words
What is it for?
Use it to fetch unread messages, identify their senders and channels, group them as action items, information, questions, or requests, acknowledge them, and recommend what to handle first.
Why use it?
It prevents unread requests, questions, and important updates from being overlooked while keeping the inbox marked accurately.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the fakechat plugin — 9 skills shipped together

Good fit Use it to fetch unread messages, identify their senders and channels, group them as action items, information, questions, or requests, acknowledge them, and recommend what to handle first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cookjohn/teammcp/check-inbox
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 cookjohn/teammcp --skill check-inbox
Clone the repo
git clone --depth 1 https://github.com/cookjohn/teammcp

Made for: Claude Code.

Or install fakechat, the plugin that ships this one along with the rest of its 9 skills.

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 check-inbox

README.md
[![agentmods](https://agentmods.dev/badge/skills/cookjohn/teammcp/check-inbox.svg)](https://agentmods.dev/skills/cookjohn/teammcp/check-inbox)
Your own site
<a href="https://agentmods.dev/skills/cookjohn/teammcp/check-inbox"><img src="https://agentmods.dev/badge/skills/cookjohn/teammcp/check-inbox.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00029 $0.00479
Opus 5 $0.00015 $0.00239
Sonnet 5 $0.00006 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured 8d ago against content hash 67e6ad0e24e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

check-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 8d 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.

plugin-dist/templates/skills/check-inbox/SKILL.md · 49 lines

What it actually says

Check & Process Inbox

Instructions

  1. Fetch unread messages

    • Call get_inbox to retrieve all unread inbox items.
    • If the inbox is empty, report "No unread messages" and stop.
  2. Review each item

    • For each unread message, identify:
      • Sender: who sent it
      • Channel or DM: where it came from
      • Content: the message body
      • Priority: whether it requires immediate action, is a question, an FYI, or a task request
  3. Categorize messages

    • Group messages into categories:
      • Action Required — messages that need a response or decision
      • FYI / Informational — status updates, notifications
      • Questions — questions directed at you that need answers
      • Tasks / Requests — work items or review requests
  4. Acknowledge processed items

    • For each reviewed message, call ack_inbox with the message ID to mark it as read.
    • Only acknowledge after you have fully reviewed the content.
  5. Generate summary

    • Output a structured summary with:
      • Total unread count
      • Breakdown by category
      • List of items requiring immediate attention (with sender and brief description)
      • Any items you recommend responding to first
  6. Respond if needed

    • If $ARGUMENTS includes "respond", also draft and send replies to urgent items using send_message (for channels) or send_dm (for direct messages).
    • Without the "respond" argument, only summarize — do not send any replies.

$ARGUMENTS

  • /check-inbox — Check inbox and summarize only
  • /check-inbox respond — Check inbox, summarize, and respond to urgent items
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. 8d ago First seen · 49 lines · 29 tokens per session scan A 67e6ad0e24e5

Subscribe to this mod's changes

check-inbox is a skill published in the GitHub repository cookjohn/teammcp (53 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 479 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-30.