A tool for watching the output of a running command as new lines arrive over time. It can start, read, list, and stop monitors for logs, builds, files, directories, or other ongoing feeds.

Use it to tail logs, follow build output, watch directory snapshots, or detect changes in a command's output. It is not intended for a single snapshot or for interpreting the data itself.

It avoids repeatedly rerunning commands to find out whether something changed. It also lets you follow a continuous process without waiting for it to finish.

monitor — Skill for Claude Code and Codex by KonghaYao/peri

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 KonghaYao/peri --skill monitor

Clone the repo

git clone --depth 1 https://github.com/KonghaYao/peri

Made for: Claude Code, 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/konghayao/peri/monitor/github.svg)](https://agentmods.dev/skills/konghayao/peri/monitor)

Your own site

<a href="https://agentmods.dev/skills/konghayao/peri/monitor"><img src="https://agentmods.dev/badge/skills/konghayao/peri/monitor/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/konghayao/peri/monitor"><img src="https://agentmods.dev/badge/skills/konghayao/peri/monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,294 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.00068	$0.02294
Opus 5.5	$0.00027	$0.00918
Sonnet 5.5	$0.00014	$0.00459
Haiku 4.5	$0.00007	$0.00229

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

Security

Grade A, and why

monitor 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 yesterday.

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.

mcp-packages/workspace/src/resources/builtin/skills/monitor/SKILL.md · 217 lines

How it starts

The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Monitor

You have access to monitor tools (mcp__monitor__monitor_start, mcp__monitor__monitor_read, mcp__monitor__monitor_stop, mcp__monitor__monitor_list) for running one shell command and reading its stdout/stderr as incremental line events.

These tools are deferred: they are not in your direct tool list. Discover them with SearchExtraTools (search for monitor), then invoke them by their full name with ExecuteExtraTool.

MonitorMCP does not understand your business data. It does not diff files, parse logs, or decide what matters. Your command should emit only the lines worth observing, and you own the comparison.

When to Use

The user asks to watch a file, log, directory, build, or feed over time.
The user asks to detect changes ("tell me when X changes", "watch this").
A command already runs continuously and emits lines; use a monitor to read them incrementally instead of repeatedly rerunning it.
Do not use a monitor for a one-shot snapshot: run the command once and read its output directly.

Tools

Tool	Purpose
`mcp__monitor__monitor_start(command, cwd?, label?, alert?, deadline_ms?, max_events?, max_bytes?)`	Start a command. The receipt gives `task_id` (host task panel) and `monitor_id` (monitor tools and `tasks/get`).
`mcp__monitor__monitor_read(task_id, after_seq?, limit?, max_bytes?)`	Read events after an exclusive cursor. Pass `monitor_id` as `task_id`.
`mcp__monitor__monitor_stop(task_id, reason?)`	Stop the command (idempotent). Pass `monitor_id` as `task_id`.
`mcp__monitor__monitor_list(include_ended?, limit?)`	List this session's monitor summaries; each `taskId` is a monitor id accepted by the monitor tools and `tasks/get`.

Task ids

The start receipt exposes two ids. They are different namespaces:

task_id (mcp-...): the host background task id. It is for host task management and the host Tasks panel only. Do not use it with the monitor tools or MCP tasks/get.
monitor_id (monitor-...): the monitor-side id. Pass it as the task_id argument of monitor_read and monitor_stop; MCP tasks/get and tasks/cancel also accept it. monitor_list reports it as each summary's taskId.

Read the full file on GitHub · 217 lines

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.

yesterday First seen · 217 lines · 68 tokens per session scan A bd6deee098e6

Subscribe to this mod's changes

monitor is a skill published in the GitHub repository KonghaYao/peri (249 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 2,294 once invoked, about $0.0003 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-11-03.

Claude Code DevOps and cloud GLM acp coding-agent deepseek mcp

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openinterpreter/openinterpreter · 114 tokens

plugin-creator

Create and scaffold plugin directories for Codex with a required .codex-plugin/plugin.json, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries…

openinterpreter/openinterpreter · 86 tokens

codex-pr-body

Update the title and body of one or more pull requests.

openinterpreter/openinterpreter · 17 tokens

remote-tests

Testing against remote executors in integration tests.

openinterpreter/openinterpreter · 12 tokens

update-v8-version

Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.