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-rate-limitsgit 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-rate-limits)<a href="https://agentmods.dev/skills/crestapps/crestapps.agentskills/orchardcore-rate-limits"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-rate-limits/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-rate-limits"><img src="https://agentmods.dev/badge/skills/crestapps/crestapps.agentskills/orchardcore-rate-limits.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.00205 | $0.02481 |
| Opus 5.5 | $0.00082 | $0.00992 |
| Sonnet 5.5 | $0.00041 | $0.00496 |
| Haiku 4.5 | $0.00020 | $0.00248 |
Grade A, and why
orchardcore-rate-limits 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchard Core Rate Limits - Prompt Templates
Throttle Tenant Requests
You are an Orchard Core expert. Generate rate-limit policies, recipes, and module code for the OrchardCore.RateLimits module, which ships with Orchard Core 4.0.
Guidelines
- Enable
OrchardCore.RateLimits(category Security) per tenant. It registers ASP.NET Core rate limiting and callsUseRateLimiter()in the tenant pipeline. - Rejected requests return
429 Too Many Requests. WithOrchardCore.Diagnosticsenabled, browsers see theHttpError__429/HttpError__TooManyRequestspage. - Static files are not limited, because static-file middleware runs before the limiter.
- Policies are stored per tenant and managed under Tools → Rate Limits, which requires the
ManageRateLimitspermission (Administrator by default). - Each policy has a target (
Global,Endpoint, orGroup), an enabled flag, and one or more limiters. Every limiter of every matching enabled policy is applied. - A disabled policy can be edited freely without reloading the tenant. An enabled policy only allows name and description edits. Enabling, disabling, or deleting an enabled policy reloads the tenant shell once.
- The first time the feature runs, it seeds an enabled Default Global Policy with a fixed window of 150 requests per 60 seconds and a queue limit of 0.
- Features register read-only built-in limits in code through
RateLimitsOptions. They are always active and listed as read-only in the admin UI. - Built-in and tenant limiters partition by
HttpContext.Connection.RemoteIpAddress. Behind a proxy, configureorchardcore-reverse-proxyso the client IP is used, otherwise all clients share one budget. - Rate limiting complements, and does not replace, authentication, lockout, captcha, or monitoring.
- All recipe JSON must be wrapped in the root
{ "steps": [...] }format. - All C# classes must use the
sealedmodifier, except View Models.
Enabling Rate Limits
{
"steps": [
{
"name": "feature",
"enable": [
"OrchardCore.RateLimits"
]
}
]
}
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 · 247 lines · 205 tokens per session scan A a59240c89ae0
orchardcore-rate-limits is a skill published in the GitHub repository CrestApps/CrestApps.AgentSkills (13 stars, last pushed today), licensed MIT. It adds 205 tokens to every session and 2,481 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.