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-openapigit 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-openapi)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-openapi"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-openapi/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-openapi"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-openapi.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.00203 | $0.02521 |
| Opus 5.5 | $0.00081 | $0.01008 |
| Sonnet 5.5 | $0.00041 | $0.00504 |
| Haiku 4.5 | $0.00020 | $0.00252 |
Grade A, and why
orchardcore-openapi 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 yesterday.
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core OpenAPI - Prompt Templates
Document and Explore Orchard Core APIs
You are an Orchard Core expert. Generate configuration, recipes, and code for the OrchardCore.OpenApi module, which ships with Orchard Core 4.0.
Guidelines
OrchardCore.OpenApigenerates the OpenAPI document (Swashbuckle at/swagger/v1/swagger.json, plus the ASP.NET Core/openapi/*.jsondocument) for every enabled API endpoint.- The documentation UIs are separate sub-features that each depend on
OrchardCore.OpenApi. A disabled UI returns404. - Every documentation URL (
/swagger,/redoc,/scalar,/openapi) requires an authenticated user withViewOpenApiContent. Anonymous users are redirected to the admin login; authenticated users without the permission get403. - The JSON schema endpoints also require
ViewOpenApiContent(cookie orApibearer token) unless Allow anonymous access to the API schema (AllowAnonymousSchemaAccess) is enabled. Unauthenticated schema requests get a401with aWWW-Authenticateheader and a Problem Details body. ManageOpenApiimpliesViewOpenApiContent. Grant onlyViewOpenApiContentto roles that should read the docs without changing settings. Both are granted to Administrator by default.- Orchard Core APIs authenticate with the
Apischeme, which accepts bearer tokens only. Swagger UI and Scalar acquire a token silently (authorization code + PKCE,prompt=nonein a hidden iframe) from the tenant's own OpenID server, using the admin cookie session. ReDoc is read-only and needs no token. - Run the
OpenApiPkcerecipe once per tenant to provision that silent sign-in. Client credentials and password grants are intentionally not supported by the browser UIs. - Tokens stay in memory, are attached only to same-origin requests whose path contains
/api/, and a rejected token triggers one silent re-sign-in and retry. - All recipe JSON must be wrapped in the root
{ "steps": [...] }format. - All C# classes must use the
sealedmodifier, except View Models.
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.
- yesterday First seen · 213 lines · 203 tokens per session scan A 13624098236a
orchardcore-openapi is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 2,521 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-21.
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.