monitor

monitor is a skill for Claude Code, Codex from agentlas-ai/agentlas-desktop. It costs 16 tokens per session (509 once invoked), scanned A, original, Apache-2.0.

A research-monitoring workflow for saving a research question, running evidence briefings, and reviewing or pausing scheduled checks. A schedule is a repeated automatic run at set times.

In plain words
What is it for?
Use it to create research monitors, run them, inspect their history and reports, update their questions or sources, and schedule or pause future checks.
Why use it?
It removes the need to repeat the same research manually and keeps previous runs available for comparison. It also makes it possible to change or pause a monitor without creating an accidental duplicate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create research monitors, run them, inspect their history and reports, update their questions or sources, and schedule or pause future checks.

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

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.

agentmods badge for monitor

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/monitor/github.svg)](https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/monitor)
Your own site
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/monitor"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/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.

agentmods 80×15 button for monitor

Your own site · 80×15
<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/monitor"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 509 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.00016 $0.00509
Opus 5.5 $0.00006 $0.00204
Sonnet 5.5 $0.00003 $0.00102
Haiku 4.5 $0.00002 $0.00051

Measured 3d ago against content hash 1d0d3429b876, 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 3d 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.

plugins/finance/skills/monitor/SKILL.md · 23 lines

How it starts

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

Monitor workflow

Read the workspace, resolve saved assets, then finance.monitor.create with a name, research query, asset IDs and current revision. This creates a draft. finance.monitor.run executes the saved research and returns an actual run result; finance.monitor.runs retrieves history and report references.

To change an existing monitor, use finance.monitor.update with its saved ID, current workspace revision and only the changed name, research query or asset IDs. Reload the returned workspace to confirm the same monitor changed; do not create a duplicate. An active schedule must be paused first, and a running check must finish before its research definition can change.

For an explicitly requested recurring schedule, finance.monitor.schedule supports every-5m, hourly, daily-09:00 and weekday-09:00. These are host scheduler times, not an inferred market calendar. Describe only the returned execution availability; app-running is not an always-on cloud guarantee. Use finance.monitor.pause when asked to stop future scheduled executions. Pausing does not claim to cancel an already running execution.

These monitors retrieve evidence and produce research briefings. They do not promise tick-by-tick price alerts, exchange-session coverage, automatic trading or a fixed provider/LLM cost. Source outages and configured model limits can produce partial or failed runs. Distinguish draft, scheduled, running, partial, failed and succeeded from the actual receipts.

Use a clear company/topic question in the requested report language. The monitor combines available asset news, prices, issuer evidence and relevant public discussion; unavailable sources remain coverage gaps. Its briefing should state the conclusion and material uncertainty without listing raw rows. The separate Finance settings toggle enables the Pro-or-higher daily holdings review through One Supervisor; a research monitor schedule is not proof that this daily review was enabled or delivered.

Read the full file on GitHub · 23 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.

  1. 3d ago First seen · 23 lines · 16 tokens per session scan A 1d0d3429b876

Subscribe to this mod's changes

monitor is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 509 once invoked, about $0.0001 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-10-19.

Related

Other skills, from other repositories

electron-expert

Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.

personamanagmentlayer/pcl · 59 tokens

architecture-diagram

How to draw and maintain the architecture diagram Ensemblr keeps for a workspace — ensemblrgetarchitecturediagram to fetch the stored one (it answers with null when nobody has drawn this workspace yet), the IR shape, how to derive it from the codebase, and ensemblrupdatearchitecturediagram to store it. Read this when…

ensemblr-hq/ensemblr · 94 tokens

ensemblr

How Ensemblr works from inside it — the workspace/git-worktree model, the ensemblr control tools and what their answers mean, the committed .ensemblr/settings.toml (setup and run scripts, [git], [prompts], [infisical], environment variables), /.config/ensemblr/config.json, the Changes panel and diff comments, the…

ensemblr-hq/ensemblr · 130 tokens

notifications

Send notifications through the unified notification router.

vellum-ai/vellum-assistant · 9 tokens

sales-icp

Build a comprehensive Ideal Customer Profile (ICP) for any B2B business - firmographic, technographic, behavioral, pain-point, budget, and channel dimensions, plus negative ICP, 100-point scoring rubric, buyer personas, prospecting playbook, and a draft first-outreach message that inherits sales-outreach Phase 0…

FerroxLabs/wayland · 181 tokens

customer-support-specialist

Becomes a seasoned customer support specialist who triages issues, crafts empathetic responses, manages escalation workflows, and builds knowledge base articles for recurring problems. Use when the user needs help writing customer responses, classifying support tickets, designing escalation procedures, or creating FAQ…

FerroxLabs/wayland · 96 tokens