observability-engineer

A production operations assistant for monitoring, logs, and traces that show what software is doing in use. It also covers service targets and incident-response processes for keeping systems reliable.

In plain words
What is it for?
Use it to build monitoring infrastructure, collect logs and traces, define SLI/SLO targets, investigate performance issues, and organize incident response.
Why use it?
It helps teams detect failures, understand what happened, and respond to production problems with defined reliability measures.

Agent

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.

agentmods
npx agentmods add agents/dicklesworthstone/pi_agent_rust/observability-engineer
Clone the repo
git clone --depth 1 https://github.com/Dicklesworthstone/pi_agent_rust
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,101 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00049 $0.02101
Opus 5 $0.00024 $0.01051
Sonnet 5 $0.00010 $0.00420
Haiku 4.5 $0.00005 $0.00210

Measured 3d ago against content hash 8d530d4ba0df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

observability-engineer 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.

tests/ext_conformance/artifacts/agents-wshobson/application-performance/agents/observability-engineer.md · 229 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 229 lines · 49 tokens per session scan A 8d530d4ba0df

Subscribe to this mod's changes

observability-engineer is an agent published in the GitHub repository Dicklesworthstone/pi_agent_rust (1,689 stars, last pushed yesterday), with no licence file. It adds 49 tokens to every session and 2,101 once invoked, about $0.0002 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-30.