universal-remote-control: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from sidkandan/universal-remote-control. Its token cost is not measured, scanned A, a copy of SessionStart, MIT.

A post-tool hook: a command that runs automatically after another tool call finishes. It executes inbox-check.sh from the project's hooks directory using Bash.

In plain words
What is it for?
It is for projects that use an inbox or remote-control bridge and need to check it after tool calls. The input does not explain what the script finds or changes.
Why use it?
It checks for new messages or work after each tool operation, so an agent does not need to run the inbox check manually.

Hook for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable.

This is sidkandan/universal-remote-control's own configuration. It tells Claude Code how to work on universal-remote-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything universal-remote-control configures →

Part of the urc plugin — 2 skills, 1 agent, 5 hooks, 2 MCP servers shipped together

One of 5 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 4 are separate, each on its own page.

Reuse

Borrowing it

Nothing to install: this file belongs to sidkandan/universal-remote-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sidkandan/universal-remote-control/master/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/sidkandan/universal-remote-control

Made for: Claude Code.

Or install urc, the plugin that ships this one along with the rest of its 2 skills, 1 agent, 5 hooks, 2 MCP servers.

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 PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/sidkandan/universal-remote-control/post-tool-use/github.svg)](https://agentmods.dev/hooks/sidkandan/universal-remote-control/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/sidkandan/universal-remote-control/post-tool-use"><img src="https://agentmods.dev/badge/hooks/sidkandan/universal-remote-control/post-tool-use/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 PostToolUse

Your own site · 80×15
<a href="https://agentmods.dev/hooks/sidkandan/universal-remote-control/post-tool-use"><img src="https://agentmods.dev/badge/hooks/sidkandan/universal-remote-control/post-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 44% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

PostToolUse 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 commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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.

Origin

This is a copy

44% identical to SessionStart — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/settings.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "bash \"$CLAUDE_PROJECT_DIR\"/hooks/scripts/inbox-check.sh"
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.

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. 1mo ago First seen · 13 lines scan A dda7daebd4c2

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository sidkandan/universal-remote-control (14 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it A with 0 findings. It is 44% identical to SessionStart, differing in 8 lines, and is treated as a copy.