agentmods.dev

local-service-monitoring

local-service-monitoring is a skill for Claude Code, Codex from CodeInfinity1/Stram. It costs 34 tokens per session (373 once invoked), scanned A, original, MIT.

A guide for checking the health and readiness of local services such as browser backends, voice services, automation daemons, and local servers.

In plain words
What is it for?
Use it to monitor service status, inspect logs when needed, and set bounded checks or triggers when ongoing monitoring is requested.
Why use it?
It shows whether a service is currently available and records gaps without pretending that a single check proves permanent health.

Skill for Claude CodeCodex

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

not rated 11repo 2mo ago A scan 34 tokens original MIT

Good fit Use it to monitor service status, inspect logs when needed, and set bounded checks or triggers when ongoing monitoring is requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codeinfinity1/stram/local-service-monitoring
View source ↗ CodeInfinity1/Stram
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 CodeInfinity1/Stram --skill local-service-monitoring
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

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 local-service-monitoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/codeinfinity1/stram/local-service-monitoring/github.svg)](https://agentmods.dev/skills/codeinfinity1/stram/local-service-monitoring)
Your own site
<a href="https://agentmods.dev/skills/codeinfinity1/stram/local-service-monitoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/local-service-monitoring/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 local-service-monitoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/codeinfinity1/stram/local-service-monitoring"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/local-service-monitoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 373 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.00034 $0.00373
Opus 5.5 $0.00014 $0.00149
Sonnet 5.5 $0.00007 $0.00075
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade A, and why

local-service-monitoring 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 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/desktop-control/local-service-monitoring/SKILL.md · 67 lines

What it actually says

Local Service Monitoring

Purpose

Keep local assistant services observable without hidden or noisy monitoring. This skill checks readiness and can create bounded wakeups/triggers when the user wants ongoing watch.

When To Use

Use for Ollama, voice wakeup, browser live backend, automation daemon, channels, local servers, and provider readiness.

Inputs And Evidence

  • Service name, endpoint/process, expected state, check cadence, and alert behavior.
  • Status tool output and logs if available.

Tool Map

  • system_status
  • external_integrations_status
  • voice_provider_status
  • browser_live_status
  • channel_doctor
  • cognitive_trigger_record
  • activity_ingest

Workflow

  1. Identify service and expected healthy state.
  2. Use native status tools first.
  3. Run bounded shell checks only when approved/needed.
  4. Record gaps and next setup steps.
  5. Create monitoring triggers only on user request.
  6. Report health as current-time evidence, not permanent truth.

Native Implementation Boundaries

  • Use Stram status/trigger tools.
  • Do not import external reference active-maintenance code.
  • Do not run hidden background loops.

Safety And Approval

  • Avoid exposing env/secrets in status.
  • Starting/stopping services requires approval.
  • Keep monitoring cadence reasonable.

Verification

  • Status outputs prove current readiness.
  • Trigger IDs prove scheduled monitoring.
  • Report unsupported checks.

Failure Modes

  • Saying a service is ready from catalog support.
  • Creating noisy monitors.
  • Ignoring resource limits.

References

  • Shortlist item: local-service-monitoring.
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 · 67 lines · 34 tokens per session scan A f813668b2da3

Subscribe to this mod's changes

local-service-monitoring is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 373 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-09-03.

DevOps and cloudai-agentai-agentsai-toolsdesktop-automationdesktop-automation-softwaredesktop-automation-windows
Related

Other skills, from other repositories

android-pentest

A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.

Netw0rkNoob/VulnClaw · 32 tokens

lighting-report-extract

Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.

AlpacaLabsLLC/skills-for-architects · 37 tokens

authentication-patterns

OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.

travisjneuman/.claude · 28 tokens

container-debugging

Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.

WrongStack/WrongStack · 45 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens