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.
npx skills add holon-run/holon --skill holon-runtime-opsgit clone --depth 1 https://github.com/holon-run/holonWrote 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/skills/holon-run/holon/holon-runtime-ops)<a href="https://agentmods.dev/skills/holon-run/holon/holon-runtime-ops"><img src="https://agentmods.dev/badge/skills/holon-run/holon/holon-runtime-ops/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/skills/holon-run/holon/holon-runtime-ops"><img src="https://agentmods.dev/badge/skills/holon-run/holon/holon-runtime-ops.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.00028 | $0.02685 |
| Opus 5 | $0.00014 | $0.01342 |
| Sonnet 5 | $0.00006 | $0.00537 |
| Haiku 4.5 | $0.00003 | $0.00268 |
Grade A, and why
holon-runtime-ops 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.
How it starts
The opening of the file, as written. The whole thing — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Holon Runtime Operations Skill
Summary
Use this skill to inspect Holon runtime health, diagnose agent and lifecycle failures, maintain incremental error checkpoints, produce explicitly authorized patrol reports, and prepare sanitized upstream bug reports.
This skill extends the platform-neutral ops workflow. It does not grant
credentials, remediation authority, scheduled execution, direct database
access, or GitHub publication authority.
When To Use
- diagnosing Holon daemon, agent, WorkItem, task, wait, timer, event-ingress, provider, tool, workspace, or delivery behavior
- preparing an authorized Holon restart, upgrade, rollback, or recovery
- counting and deduplicating new Holon runtime errors
- running an explicitly configured report-only patrol
- preparing or publishing a sanitized
holon-run/holonissue under the applicable bug-reporting policy
Do Not Use
- for general server or service administration unrelated to Holon
- to read task objectives, messages, prompts, transcripts, memory, or model request bodies for an activity report
- to turn a diagnosis or patrol authorization into repair authority
- to access the runtime database by default or depend on a private schema
- to publish security, privacy, credential, personal-data, or corruption findings automatically
Authority Gates
Treat these as separate authorizations:
- read-only runtime diagnosis
- maintenance or remediation
- scheduled patrol
- anomaly notification
- direct runtime-database read
- direct runtime-database write
- GitHub duplicate search
- issue draft creation
- issue publication
Record the scope, source, expiry, and revocation conditions of standing authorizations. If a gate is absent or ambiguous, stop at the last authorized step and report what is needed next.
Source Priority
Collect evidence in this order:
- native runtime tools for their declared responsibility
- declared machine-readable
holonCLI commands - authoritative service or deployment logs
- deployment configuration and version metadata
- separately authorized read-only runtime-database queries as a final deep-diagnostic fallback
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 · 386 lines · 28 tokens per session scan A ed0093e19483
holon-runtime-ops is a skill published in the GitHub repository holon-run/holon (135 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 2,685 once invoked, about $0.0001 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-09-07.
Other skills, from other repositories
google-workspace-setup
One-time setup for gws: install, OAuth, scopes, auto-approve.
attachments
Move bytes between Gini upload space, external URLs, and workspace files. Used by every attachment / file-upload / file-download flow regardless of the target system (Linear, GitHub, S3, Notion, etc.).
google-docs
Google Docs via gws: read, append text, structured batch edits.
google-forms
Google Forms via gws: create forms, add items, read responses.
google-sheets
Google Sheets via gws: read/write cells, append rows, structured batch edits.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.