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 lukas-grigis/ralphctl --skill ralphctl-observability-and-instrumentationgit clone --depth 1 https://github.com/lukas-grigis/ralphctlWrote 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/lukas-grigis/ralphctl/ralphctl-observability-and-instrumentation)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/ralphctl-observability-and-instrumentation"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-observability-and-instrumentation/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/lukas-grigis/ralphctl/ralphctl-observability-and-instrumentation"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/ralphctl-observability-and-instrumentation.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.00108 | $0.01343 |
| Opus 5.5 | $0.00043 | $0.00537 |
| Sonnet 5.5 | $0.00022 | $0.00269 |
| Haiku 4.5 | $0.00011 | $0.00134 |
Grade A, and why
ralphctl-observability-and-instrumentation 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability and Instrumentation
Adapted from addyosmani/agent-skills — "Observability and Instrumentation" (MIT). Adapted for ralphctl's harness contract.
Code you cannot observe is code you cannot operate. Instrumentation is written with the feature, the way tests are — when it ships without telemetry, the first reported bug becomes archaeology instead of a query.
Not for: diagnosing a failure happening now (ralphctl-debugging-and-error-recovery when installed), or optimising measured slowness (ralphctl-performance-optimization when installed).
When this applies
- Plan — for tasks that add I/O, retries, queues, jobs, or integrations, put the telemetry in the task's steps and add a verification criterion that the failure path is observable. Name the operator questions it must answer.
- Execute — instrument as you build, with the logging, metrics, and tracing libraries the project already uses. Adding a new telemetry stack is a decision for the task to make, not a side effect.
1. Define "working" first
Telemetry without a question is noise. Before instrumenting, write down two to four questions an operator will ask about this feature — what fraction succeeds first time, why permanent failures fail, whether a dependency is slower than usual. Every signal you add must help answer one of them.
2. Pick the signal per question
| Signal | Answers | Cost |
|---|---|---|
| Structured log | What happened in this specific case? | Per event; grows with traffic |
| Metric | How often, how fast, in aggregate? | Fixed per series; cheap |
| Trace | Where did the time go across components? | Per request; usually sampled |
Metrics tell you that something is wrong, traces tell you where, logs tell you why.
3. Structured logging
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 · 105 lines · 108 tokens per session scan A f53fd1044ce9
ralphctl-observability-and-instrumentation is a skill published in the GitHub repository lukas-grigis/ralphctl (24 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 1,343 once invoked, about $0.0004 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-18.
Other skills, from other repositories
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…
review
Review local code changes for bugs, regressions, missing tests, and pragmatic improvements. Use when the user asks to review the current changes from git status, or to review a specific backlog task by id such as task-65 or TASK-65. Also trigger when the user says things like "review", "review current changes", "check…
web-access
A method for handling difficult web tasks across search, page fetching, and a real browser. It covers sites that need login sessions, dynamic pages, anti-bot handling, or exploration before their structure is understood.
skill-creator
A skill for creating or improving reusable instructions for an agent. It covers capturing the intended workflow, writing a draft, testing it, and refining its trigger description.
repo
Repository operating rules for verified Mythos edits.
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from docs/plans, a spec path, or a clear build request; use ce-debug for open-ended bugs.