Borrowing it
Nothing to install: this file belongs to stellar-experimental/stellar-raven. 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/stellar-experimental/stellar-raven/main/.agents/skills/cloudflare-observability-review/SKILL.mdgit clone --depth 1 https://github.com/stellar-experimental/stellar-ravenWrote 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/stellar-experimental/stellar-raven/cloudflare-observability-review)<a href="https://agentmods.dev/skills/stellar-experimental/stellar-raven/cloudflare-observability-review"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/cloudflare-observability-review/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/stellar-experimental/stellar-raven/cloudflare-observability-review"><img src="https://agentmods.dev/badge/skills/stellar-experimental/stellar-raven/cloudflare-observability-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 98 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00069 | $0.04847 |
| Opus 5.5 | $0.00028 | $0.01939 |
| Sonnet 5.5 | $0.00014 | $0.00969 |
| Haiku 4.5 | $0.00007 | $0.00485 |
Grade A, and why
cloudflare-observability-review scanned grade A with 1 finding 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 28d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -i -sS https://raven.stellar.org/mcp \ How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Observability Review
Use this runbook to answer "what happened in production?" for
stellar-raven-codemode using Cloudflare Workers Logs, platform invocation
events, and OTel spans.
When the investigation is part of an eval round, agent-run forensic review, or other
multi-agent maintenance pass, record the query inputs, Ray IDs, and verdict in the relevant
round ledger (.agents/rounds/) or .agents/TODO.md so the evidence survives outside the
current context window.
Principle
Prefer Cloudflare-native request identity for one invocation. Use the app's privacy-safe OAuth subject/client hashes only for cross-request attribution.
Observability works without a model-facing correlationId contract. Same-user
concurrent MCP tasks are rare, and for debugging/evals we join requests by Ray ID,
time window, user-agent/client marker, host/path/method/status, and auth mode. If an
investigation needs stronger cross-request grouping, add privacy-safe auth
subject/client fields to app logs rather than asking models to forward ids.
Safety Rules
- Never print secrets from
.env,.dev.vars, Wrangler, Cloudflare, or MCP responses. - Use Cloudflare API MCP for historical evidence.
wrangler tailis only a convenience stream; a miss there is not evidence that logs are absent. - Do not copy raw IPs, IP hashes, or IP-derived fingerprints into app logs. Cloudflare platform events already expose IP-bearing request headers.
- It is OK to query and use Cloudflare-native private/platform fields (IP-bearing headers, geo, TLS/client fingerprint fields, user-agent) inside a bounded investigation when they are needed to join or separate requests. Report them only when directly relevant; otherwise report Ray IDs, time windows, paths, statuses, and app event fields.
- Do not infer identity from IP/geo/TLS fields unless explicitly doing an abuse review with a separate privacy decision.
What Joins Reliably
For one HTTP invocation:
- Response
cf-rayheader -> Workers Logs. Strip the colo suffix:a15a1ed37fa5b049-ATL->a15a1ed37fa5b049. - Workers app JSON logs:
$metadata.type = "cf-worker". - Workers platform invocation logs:
$metadata.type = "cf-worker-event". - OTel spans:
$metadata.type = "span", joined bycloudflare.ray_id.
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.
- 28d ago Changed · +2 lines 1ca90d1afd0d
- 29d ago Changed 622dcc8bdff1
- 1mo ago First seen · 383 lines · 69 tokens per session scan A d857cf680a63
cloudflare-observability-review is a skill published in the GitHub repository stellar-experimental/stellar-raven (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 4,847 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
azure-kubernetes-automatic-readiness
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic…
azure-diagnostics
Debug Azure production issues using AppLens, Azure Monitor, resource health, and safe triage, including evidence-only diagnosis without live access. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target…
workers-profiling
Profile or debug CPU usage and memory allocation in deployed Cloudflare Workers and Durable Objects. Then use this information to optimize your code.
hyperpod-node-debugger
Diagnose and remediate per-node issues on a HyperPod cluster (EKS or Slurm) — a specific node is unhealthy, unresponsive, stuck, or needs replacing. Covers on-node EFA, GPU / accelerator hardware (XID, ECC, NVLink, row-remap, DCGM), Slurm node down/drained, disk and memory pressure, per-node lifecycle-script failures…
hyperpod-cluster-debugger
Diagnose and remediate cluster-wide HyperPod (EKS or Slurm) problems — creation / deployment failures (CloudFormation, EFA health check, lifecycle scripts, capacity), EKS access, node replacement, CloudFormation nested-stack errors, post-maintenance rollback state, dangling nodes, autoscaler conflicts. Includes…
hyperpod-nccl
Diagnose NCCL failures and adjacent training-pod failures on HyperPod GPU clusters (EKS or Slurm) — training hangs, AllReduce / collective-op timeouts, EFA or libfabric errors, rendezvous failures, EFA TCP fallback, /dev/shm or memlock issues, NCCL version mismatch across pods, container OOM / exit-137 / OOMKilled…