What is investigate-removed-item?

A guided workflow for investigating events where an object was detected as removed. It checks event details and verifies whether the related evidence is intact.

Checking when and where an object disappeared, what type it was, how the count changed, how the event was handled, and whether its evidence passed verification.

It separates what the recorded evidence proves from what it does not, such as identifying who caused the removal.

investigate-removed-item — Skill for Codex by zja0011

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 zja0011/edgesentinel-visionops --skill investigate-removed-item

Clone the repo

git clone --depth 1 https://github.com/zja0011/edgesentinel-visionops

Made for: Codex.

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/skills/zja0011/edgesentinel-visionops/investigate-removed-item/github.svg)](https://agentmods.dev/skills/zja0011/edgesentinel-visionops/investigate-removed-item)

Your own site

<a href="https://agentmods.dev/skills/zja0011/edgesentinel-visionops/investigate-removed-item"><img src="https://agentmods.dev/badge/skills/zja0011/edgesentinel-visionops/investigate-removed-item/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/skills/zja0011/edgesentinel-visionops/investigate-removed-item"><img src="https://agentmods.dev/badge/skills/zja0011/edgesentinel-visionops/investigate-removed-item.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 334 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.00052	$0.00334
Opus 5	$0.00026	$0.00167
Sonnet 5	$0.00010	$0.00067
Haiku 4.5	$0.00005	$0.00033

Measured 12d ago against content hash 04a736054c39, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

investigate-removed-item 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 12d 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.

skills/investigate-removed-item/SKILL.md · 29 lines

What it actually says

Investigate a removed item

Use this workflow when the user asks whether an object was removed, asks to investigate a removal, or asks who took an object.

Call event.query with event_type=OBJECT_REMOVED, a bounded limit, and the exact detector object_class when the user states one.
If an event is returned and more detail or evidence integrity is necessary, call event.get_detail and evidence.verify_event for the same most relevant exact event_id together in one model response. Do not spread these independent reads across separate model rounds.
Report whether evidence is valid, but never claim that integrity verification identifies a person.
Keep every conclusion tied to Tool results. A removal event proves a count change, not who caused it. If no identity evidence exists, explicitly say that the responsible person cannot be determined.
Do not call tools outside required_tools. Do not acknowledge events, capture snapshots, restart the camera, generate files, or perform cleanup.

Answer in the user's language. Include event time, camera, zone, object class, count change, disposition, and evidence status only when those fields are available. State when data is stale, absent, incomplete, or outside the query window.

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

12d ago First seen · 29 lines · 52 tokens per session scan A 04a736054c39

Subscribe to this mod's changes

investigate-removed-item is a skill published in the GitHub repository zja0011/edgesentinel-visionops (22 stars, last pushed 29d ago), licensed Apache-2.0. It adds 52 tokens to every session and 334 once invoked, about $0.0003 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.

agent-harness ai-agent computer-vision deepseek disaster-recovery docker

skill

Ten native DSH tools give a text-only agent eyes. Use these structured tools directly; do not shell out to the bundled Python scripts or reproduce their implementation. Vision API credentials and model settings are managed by the plugin, so tool calls do not receive credentials.

Anionex/dsh-vision-toolkit · 0 tokens

git-commit

A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.

adongwanai/learn-workbuddy · 0 tokens

figma-use

MANDATORY prerequisite — you MUST invoke this skill BEFORE every usefigma tool call. NEVER call usefigma directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in…

Haohao-end/openagent · 114 tokens

cli-creator

Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a…

Haohao-end/openagent · 82 tokens

cloudflare-deploy

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

Haohao-end/openagent · 43 tokens

vercel-deploy

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Haohao-end/openagent · 47 tokens