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 CrestApps/CrestApps.AgentSkills --skill orchardcore-websocketsgit clone --depth 1 https://github.com/CrestApps/CrestApps.AgentSkillsWrote 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/crestapps/crestapps.agentskills/orchardcore-websockets)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-websockets"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-websockets/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/crestapps/crestapps.agentskills/orchardcore-websockets"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-websockets.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.00200 | $0.01908 |
| Opus 5.5 | $0.00080 | $0.00763 |
| Sonnet 5.5 | $0.00040 | $0.00382 |
| Haiku 4.5 | $0.00020 | $0.00191 |
Grade A, and why
orchardcore-websockets 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 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.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core WebSockets - Prompt Templates
Host Raw WebSocket Endpoints
You are an Orchard Core expert. Generate accurate code and configuration for features that accept raw WebSocket upgrades (HttpContext.WebSockets.AcceptWebSocketAsync()) in a CrestApps Orchard Core tenant.
Guidelines
- The Orchard Core host does not run
app.UseWebSockets(). Without it a raw upgrade is refused. SignalR does not need it (seeorchardcore-signalr). CrestApps.OrchardCore.WebSocketsis the single place the middleware is added. It isEnabledByDependencyOnly, so it never shows as a toggle; declare it as a dependency of your feature instead of enabling it in a recipe.- Depend on the contracts in
CrestApps.OrchardCore.WebSockets.Abstractions(IWebSocketConnectionRegistry,WebSocketRendezvous), not on the module's host wiring. - Use unguessable, single-use keys for every rendezvous, and remove the key when the starter times out.
- A live socket cannot move between nodes. Route provider callbacks back to the node that started them.
- Install third-party module packages in the web/startup project.
- All recipe JSON must be wrapped in
{ "steps": [...] }. - All C# classes must use the
sealedmodifier, except for View Models.
Feature Overview
| Item | Value |
|---|---|
| Module package | CrestApps.OrchardCore.WebSockets (category Infrastructure) |
| Feature ID | CrestApps.OrchardCore.WebSockets (WebSocketsConstants.Feature.Area) |
| Enabled by | Dependency only (for example the CrestApps.OrchardCore.Telnyx feature) |
| Contracts package | CrestApps.OrchardCore.WebSockets.Abstractions (namespace CrestApps.OrchardCore.WebSockets) |
| Configuration section | CrestApps:WebSockets (WebSocketsConstants.ConfigurationSectionPath), bound to ASP.NET Core WebSocketOptions |
| Default registry | InMemoryWebSocketConnectionRegistry (per node) |
| Distributed registry | DistributedWebSocketConnectionRegistry, active when OrchardCore.Redis is enabled |
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 · 186 lines · 200 tokens per session scan A a4ed167aa8dc
orchardcore-websockets is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 200 tokens to every session and 1,908 once invoked, about $0.0008 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-10-22.
Other skills, from other repositories
tech-specs
To define clear, testable tech specs from requirements — target-state architecture, contracts, interfaces.
sast-idor
Detect Insecure Direct Object Reference (IDOR) vulnerabilities in a codebase using a three-phase approach: recon (find candidates), batched verify (check authorization in parallel subagents, 3 candidates each), and merge (consolidate batch results). Checks endpoints for missing ownership or authorization checks on…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
add-service
Scaffold a new service integration. Use when the user asks to add a service, integrate an external API, or create a reusable domain module with its own initialization and state.
api-utils
API reference for all utilities exported from @cyanheads/mcp-ts-core/utils. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.