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 Cratis/AI --skill cratis-arc-observable-query-httpgit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-arc-observable-query-http)<a href="https://agentmods.dev/skills/cratis/ai/cratis-arc-observable-query-http"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-arc-observable-query-http.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.00082 | $0.01434 |
| Opus 5 | $0.00041 | $0.00717 |
| Sonnet 5 | $0.00016 | $0.00287 |
| Haiku 4.5 | $0.00008 | $0.00143 |
Grade A, and why
cratis-arc-observable-query-http 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 today.
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.
description: Inspect a Cratis Arc observable query from a terminal with curl or another plain HTTP client — snapshot GET, waiting for the first result, Server-Sent Events streaming, and long polling, plus the exact query How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect an Arc observable query over HTTP
An observable query endpoint answers three different ways depending on how the request is made. Choose the transport first, then the command.
Verified product sources
| Package | Version | Purpose |
|---|---|---|
Cratis.Arc.Core |
22.10.4 |
ObservableQueryHttp, ObservableQueryHandler, the demultiplexer routes |
Reverify before claiming support for another version. This skill is read-only inspection of an endpoint the user already has; it neither implements the query nor changes any state.
How Arc picks the transport
For a query whose result is an ISubject<T> or IAsyncEnumerable<T>, the
handler decides in this order:
- WebSocket — the request is a WebSocket upgrade;
- Server-Sent Events — the
Acceptheader containstext/event-stream(case-insensitive); - plain HTTP — everything else, answered once and closed.
A plain curl sends neither, so it always lands on the third case.
Snapshot: the current value, once
curl "https://<host>/<api-prefix>/<route>"
The response is one JSON QueryResult.
⚠️ When the observable has not produced its first value yet, this returns HTTP 202 Accepted with a not-ready result — no exception, no data. That is a normal transient state (a subscription that has not emitted, a page past the end of the data), not a failure. A caller that treats 202 as an error is misreading a pending query as a crash.
Wait for the first result
curl "https://<host>/<api-prefix>/<route>?waitForFirstResult=true"
curl "https://<host>/<api-prefix>/<route>?waitForFirstResult=true&waitForFirstResultTimeout=10"
| Key | Meaning |
|---|---|
waitForFirstResult |
Parsed as a boolean; anything that is not a parseable true means "do not wait" |
waitForFirstResultTimeout |
Seconds, must be greater than 0. Defaults to 30 |
Outcomes:
| Outcome | Status | Body |
|---|---|---|
| A value arrives | 200 | QueryResult with the data |
| The timeout elapses | 408 Request Timeout | An error result naming the timeout in seconds |
| The observable completes without ever emitting | 500 | An error result saying so |
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.
- today First seen · 158 lines · 82 tokens per session scan A a57427814ea3
cratis-arc-observable-query-http is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 1,434 once invoked, about $0.0004 per session on Opus 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-09-06.
Other skills, from other repositories
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
orchardcore-diagnostics
Skill for configuring Orchard Core diagnostics error handling. Covers custom error pages, status code pages, DiagnosticsStartupFilter, IConfigureOptions integration, error shapes, alternate shape names, and production exception handling. Use this skill when requests mention Orchard Core Diagnostics, custom error page…
maf-fan-out-validator
Validates fan-out / fan-in workflow topology — detects the silent fan-in starvation pattern (handlers returning void / non-generic Task that produce no downstream message). Canonical rules + procedure for what the compiler cannot catch and the build cannot surface.
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
cqrs-event-sourcing
CQRS and Event Sourcing patterns for scalable, auditable systems with separated read/write models. Use when building audit-required systems, implementing temporal queries, or designing high-scale applications with complex domain logic.
use-discatsharp
Build, explain, migrate, or troubleshoot Discord applications that use DisCatSharp. Use for DisCatSharp setup, configuration, clients, events, intents, slash commands, CommandsNext, interactivity, hosting, Lavalink, voice, entities, REST operations, exact API lookup, overload selection, and version-aware C# examples.