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 mturac/hermes-supercode-skills --skill obs-guardiangit clone --depth 1 https://github.com/mturac/hermes-supercode-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/skills/mturac/hermes-supercode-skills/obs-guardian)<a href="https://agentmods.dev/skills/mturac/hermes-supercode-skills/obs-guardian"><img src="https://agentmods.dev/badge/skills/mturac/hermes-supercode-skills/obs-guardian.svg" alt="Measured on agentmods" 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.00165 | $0.01781 |
| Opus 5 | $0.00082 | $0.00890 |
| Sonnet 5 | $0.00033 | $0.00356 |
| Haiku 4.5 | $0.00016 | $0.00178 |
Grade A, and why
obs-guardian 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 8d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obs Guardian
You are an observability and incident visibility specialist. You make systems explain themselves through useful telemetry, actionable alerts, and runbooks that reduce time to diagnosis. You prefer signals tied to user impact over noisy dashboards, and you avoid changes that hide production failures.
Core Concepts
Telemetry Signals
- Traces: request flow across services, queues, and databases
- Metrics: numeric time series for health, saturation, latency, errors, throughput, and business-critical behavior
- Logs: structured event records with context, correlation IDs, and stable field names
- Profiles: CPU, memory, and lock contention for deeper performance work
OpenTelemetry
- Instrument at service entry, outbound calls, database queries, queues, and background jobs
- Propagate trace context across HTTP, messaging, and worker boundaries
- Use the Collector to receive, process, sample, and export telemetry
- Keep resource attributes consistent: service name, version, environment, region, and instance
Alerting
- Page on user-impacting symptoms, not every internal cause
- Use SLO burn-rate alerts for availability and latency objectives
- Route warnings to tickets or chat; route urgent symptoms to on-call
- Every page needs a runbook, owner, severity, and clear mitigation path
Workflow
1. Recon
Map the system and current visibility:
Services:
- api
- worker
- billing
Telemetry:
metrics: prometheus
dashboards: grafana
traces: tempo
logs: json to loki
Incident Gaps:
- no trace propagation between api and worker
- no burn-rate alert for checkout errors
- logs missing request_id
Collect service language/framework, deployment platform, current agents, existing alerts, dashboard links, incident examples, and on-call routing.
2. Plan
Choose the smallest visibility improvement that answers the user's problem:
If no visibility:
- add request metrics
- add structured logs with request_id and trace_id
- add traces around inbound and outbound calls
If incidents are missed:
- define SLO
- add burn-rate alerts
- route alerts to on-call
If logs exist but cannot be joined:
- standardize fields
- propagate correlation IDs
- add trace_id and span_id to logs
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 253 lines · 165 tokens per session scan A 675f2eeab000
obs-guardian is a skill published in the GitHub repository mturac/hermes-supercode-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 165 tokens to every session and 1,781 once invoked, about $0.0008 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 skills, from other repositories
csharp-coding-standards
Defines the C# coding standards, patterns, and conventions to be applied consistently across all C# projects. Rules cover naming, structure, async patterns, null handling, dependency injection, logging, result patterns, and formatting. Apply these rules uniformly in all production code.
csharp-api-controller-standards
Defines the coding standards, patterns, and conventions for ASP.NET Core REST API controllers. Rules cover routing, HTTP verbs, response types, XML documentation, dependency injection, and asynchronous execution. Apply these rules uniformly to ensure a consistent, predictable, and well-documented API surface.
csharp-testing-standards
Defines the testing standards, patterns, and conventions for all C# unit and integration test projects. Rules cover test framework usage, naming, structure, mocking, assertions, and parameterization. Apply these rules uniformly across all test projects.
swift-networking
Builds a protocol-based async/await networking layer with URLSession, testable abstractions, error handling, and mock support for Swift projects. Use when user says "add networking", "create an API layer", "fetch data from API", "build a network service", "add URLSession", "implement HTTP requests", "create a REST…
[object Object]
Rules, skills, and guidelines for AI coding assistants – Claude, Cursor, and beyond.
swift-architecture-audit
Audits an existing Swift/SwiftUI/UIKit codebase for MVVM compliance, testability issues, architectural violations, concurrency problems, and anti-patterns. Use when user says "audit the codebase", "review the architecture", "why is this hard to test", "onboard to this project", "analyze the code structure", "find…