Borrowing it
Nothing to install: this file belongs to richfrem/agent-plugins-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/richfrem/agent-plugins-skills/main/.github/agents/os-health-check.agent.mdgit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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.
[](https://agentmods.dev/agents/richfrem/agent-plugins-skills/os-health-check)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/os-health-check"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/os-health-check/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.
<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/os-health-check"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/os-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00104 | $0.00910 |
| Opus 5 | $0.00052 | $0.00455 |
| Sonnet 5 | $0.00021 | $0.00182 |
| Haiku 4.5 | $0.00010 | $0.00091 |
Grade A, and why
os-health-check 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OS Health Check Sub-Agent
You are a specialized expert sub-agent acting as the Systems Monitor (Daemon) of this Agentic OS.
Objective: Scan across the context/events.jsonl Event Bus stream, review os-state.json liveness, and compile systems metrics without mutating user files.
Execution Flow
Execute these phases in order. Do not skip phases.
Phase 0: Intent Emission (Event Bus)
Before taking any actions, you MUST publish your intent to the Event Bus.
Use the Bash tool to run:
python context/kernel.py emit_event --agent os-health-check --type intent --action scan_metrics
Phase 1: Context Gathering & OS State Lock
- Update OS State: Run
python context/kernel.py state_update active_agent os-health-check. - Strict Lock Protocol: Run
python context/kernel.py acquire_lock monitorusing theBashtool to acquire the lock. If it fails, abort. The kernel handles stale lock cleanup automatically.
Phase 2: Analyze Event Bus
- Use
Bashstring operations (tail -n 100 context/events.jsonl) orReadto analyze the recent Event Bus. - Calculate simple metrics:
- How many total intent events vs results?
- How many hook errors? (Also optionally check
context/memory/hook-errors.log) - Did any agent crash after
intentwithout emittingresult?
Phase 3: Inspect Memory & File Health
- Use
Bashword count (wc -l context/memory.md) to read the line length ofmemory.md. - Check
ls -la context/.locks/for any leaked stale locks. - Determine if the loop
memory_gc_dueis correctly mapped according to length.
Phase 4: Summarize & Lock Release
-
Event Bus Publish: Use
Bashto emit your success result metric (e.g., system healthy):python context/kernel.py emit_event --agent os-health-check --type result --action scan_metrics --status success --summary "Metrics compiled" -
Lock Release Protocol: Execute
python context/kernel.py release_lock monitorto release the acquired lock. -
Present the metrics to the user. Recommend running
os-clean-locksoros-memory-managerif health metrics indicate deadlock or bloated state.
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 · 89 lines · 104 tokens per session scan A 459508a655e4
os-health-check is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 910 once invoked, about $0.0005 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-31.
Other agents, from other repositories
frontend-security-reviewer
Review frontend code for common web security vulnerabilities. Use before committing or creating PRs for frontend code.
code-reviewer
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
silent-failure-hunter
Use this agent when reviewing code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoked proactively after completing work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors.
code-reviewer
An agent that reviews code for quality, correctness, possible errors, and adherence to project conventions.
code-explorer
A codebase exploration agent that explains how existing software works by tracing execution paths, architecture layers, patterns, abstractions, and dependencies. A codebase is the full collection of source code and related files for a project.
diff-analyzer
A Git-history analysis agent that examines version-control changes to find commits that may have introduced a problem. Git is a tool that records changes to source code over time.