What is sensor-remove?

A command that removes a World2Agent sensor, a background watcher for an outside source.

Use it with a complete sensor package name to stop and uninstall that sensor, and optionally remove its handler skill.

It removes the sensor from the configuration and uninstalls its npm package, reducing unwanted monitoring.

sensor-remove — Command for Claude Code by machinepulse-ai

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add machinepulse-ai/world2agent-plugins

Claude Code

/plugin install world2agent

Made for: Claude Code.

Or install world2agent, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/machinepulse-ai/world2agent-plugins/sensor-remove/github.svg)](https://agentmods.dev/commands/machinepulse-ai/world2agent-plugins/sensor-remove)

Your own site

<a href="https://agentmods.dev/commands/machinepulse-ai/world2agent-plugins/sensor-remove"><img src="https://agentmods.dev/badge/commands/machinepulse-ai/world2agent-plugins/sensor-remove/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/machinepulse-ai/world2agent-plugins/sensor-remove"><img src="https://agentmods.dev/badge/commands/machinepulse-ai/world2agent-plugins/sensor-remove.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 249 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.

Model	Per session	Once invoked
Fable 5.1	$0.00006	$0.00249
Opus 5.5	$0.00002	$0.00100
Sonnet 5.5	$0.00001	$0.00050
Haiku 4.5	$0.00001	$0.00025

Measured 2mo ago against content hash ea1afcf7ab9c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sensor-remove 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.

claude-code-channel/commands/sensor-remove.md · 18 lines

What it actually says

Remove sensor $ARGUMENTS. $ARGUMENTS MUST be a complete npm package name (e.g. @world2agent/sensor-hackernews) — never guess, never auto-prepend a scope.

If the user gives only a short name, first run /world2agent:sensor-list to look up the exact package field in ~/.world2agent/config.json, then proceed.

Steps:

Remove the entry with package === "$ARGUMENTS" from the sensors array in ~/.world2agent/config.json.

Uninstall the npm package:

npm uninstall $ARGUMENTS --prefix "${CLAUDE_PLUGIN_ROOT}"

Derive skill_id = packageToSkillId($ARGUMENTS) (e.g. @world2agent/sensor-hackernews → world2agent-sensor-hackernews), and ask the user whether to also delete the handler skill at .claude/skills/<skill_id>/ (if present).
Prompt the user to run /reload-plugins or restart Claude Code.

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.

2mo ago First seen · 18 lines · 6 tokens per session scan A ea1afcf7ab9c

Subscribe to this mod's changes

sensor-remove is a command published in the GitHub repository machinepulse-ai/world2agent-plugins (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 6 tokens to every session and 249 once invoked, about $0.0000 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.

sensor-remove next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sensor-removemachinepulse-ai/world2agent-plugins	Command	5	7d ago	Apache-2.0	A	6	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code