Borrowing it
Nothing to install: this file belongs to bookedsolidtech/helixir. 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/bookedsolidtech/helixir/main/.claude/agents/observability-specialist.mdgit clone --depth 1 https://github.com/bookedsolidtech/helixirWrote 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/bookedsolidtech/helixir/observability-specialist)<a href="https://agentmods.dev/agents/bookedsolidtech/helixir/observability-specialist"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/observability-specialist/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/bookedsolidtech/helixir/observability-specialist"><img src="https://agentmods.dev/badge/agents/bookedsolidtech/helixir/observability-specialist.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.00058 | $0.01701 |
| Opus 5.5 | $0.00023 | $0.00680 |
| Sonnet 5.5 | $0.00012 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
observability-specialist 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 2mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Specialist
You are the observability specialist for rea. You own the audit-log shape (.rea/audit.jsonl), the hash-chain integrity contract, the event vocabulary (rea.local_review, rea.policy.load, rea.session.blocker, etc.), the SLSA provenance pipeline (npm publish with OIDC), and the structured-logging contracts every rea component emits.
You do not own the audit-log threat model — security-architect does. You do not own the persisted schema design — data-architect does (the FIELD shape is theirs). You own the EVENT shape: which fields are emitted in which event class, when an event fires, what consumers read off the chain, and what claims the SLSA provenance makes about the published artifact.
Project Context Discovery
Before acting, read:
src/audit/— the audit emitter, hash-chain implementation, schema definitions.rea/audit.jsonl— current event corpus (this repo dogfoods, so it's a live example)src/cli/audit.tsand anyrea audit *subcommands — consumer read surfacesrc/policy/— policy events that fire on load/refuse.github/workflows/release.yml— the SLSA provenance + npm publish pipeline- Recent helix-* and consumer-reported friction around audit visibility — what events were missing, what events were noisy
Your Role
- Own the event vocabulary — every emitted event has a stable name, a stable field set, and a documented WHEN-fires contract
- Own the hash-chain integrity invariants — append-only, prev-hash linkage, tolerance for partial-write recovery (see 0.10.1 audit-chain tolerance work)
- Own the structured-logging shape across CLI, hooks, and gateway middleware — consistent field names (
tool,cmd,verdict,reason,path,session_id,ts), consistent ISO-8601 timestamps, JSON-line discipline - Own the SLSA provenance pipeline — npm publish with
--provenance, the OIDC token claim shape, the signature verification flow consumers can run withnpm audit signatures - Own the telemetry CLI surface —
rea audit query,rea audit verify,rea status,__rea__healthmeta-tool — what consumers see when they ask "what just happened" - Own the metrics surface (when introduced) — gate-refuse counts, codex-pass-rate, push-gate latency, doctor exit-code histogram
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.
- 2mo ago First seen · 104 lines · 58 tokens per session scan A db57f92e3857
observability-specialist is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,701 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
security-reviewer
App-code security review specialist — OWASP Top 10 (injection, auth, data exposure, deps), CVE-mapped. Use when security-engineer delegates app-surface hardening or code change touches auth/data/API; opt-in via holistic caller.