agentmods.dev

Orleans.RateLimiting: Skill for Codex

.codex/skills/stylecop-analyzers/SKILL.md

stylecop-analyzers is a skill for Codex from managedcode/Orleans.RateLimiting. It costs 51 tokens per session (945 once invoked), scanned A, a copy of stylecop-analyzers, MIT.

A .NET code-analysis package that checks naming, layout, documentation, and other style rules. It uses .editorconfig for severity and can use stylecop.json for StyleCop-specific settings.

In plain words
What is it for?
Use it to add StyleCop.Analyzers to a .NET project and configure its style checks for development, review, or CI.
Why use it?
It makes style expectations explicit and helps find inconsistent code before review. It also helps teams avoid enabling rules that duplicate an existing analyzer package.

Skill for Codex

Written for Codex: installed under .codex/. Also seen: mentions AGENTS.md.

This is managedcode/Orleans.RateLimiting's own configuration. It tells Codex how to work on Orleans.RateLimiting itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Orleans.RateLimiting configures →

not rated 30repo 11d ago A scan 51 tokens copy · 94% MIT
View source ↗ managedcode/Orleans.RateLimiting
Reuse

Borrowing it

Nothing to install: this file belongs to managedcode/Orleans.RateLimiting. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/managedcode/Orleans.RateLimiting/main/.codex/skills/stylecop-analyzers/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/managedcode/Orleans.RateLimiting

Made for: Codex.

Wrote 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.

agentmods badge for stylecop-analyzers

README.md
[![agentmods](https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/stylecop-analyzers/github.svg)](https://agentmods.dev/skills/managedcode/orleans.ratelimiting/stylecop-analyzers)
Your own site
<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/stylecop-analyzers"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/stylecop-analyzers/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.

agentmods 80×15 button for stylecop-analyzers

Your own site · 80×15
<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/stylecop-analyzers"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/stylecop-analyzers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 945 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00945
Opus 5.5 $0.00020 $0.00378
Sonnet 5.5 $0.00010 $0.00189
Haiku 4.5 $0.00005 $0.00094

Measured 19d ago against content hash 96765166da6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stylecop-analyzers 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 19d 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.

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.

Origin

This is a copy

94% identical to stylecop-analyzers — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.codex/skills/stylecop-analyzers/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

StyleCop Analyzers

Trigger On

  • the repo wants StyleCop.Analyzers
  • naming, layout, or documentation style needs stronger enforcement
  • the team needs stylecop.json guidance

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • repos that intentionally rely only on SDK analyzers
  • repos where StyleCop overlaps too heavily with an existing style package and no consolidation is planned

Inputs

  • the nearest AGENTS.md
  • current .editorconfig
  • any existing stylecop.json

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Add StyleCop.Analyzers only if the repo wants its opinionated style rules.
  2. Keep severity in the root .editorconfig.
  3. Use stylecop.json only for StyleCop-specific behavioral options.
  4. Prefer one checked-in stylecop.json per repo unless a project genuinely needs its own behavior.
  5. Avoid rule duplication with SDK analyzers or other analyzer packs when possible.

Bootstrap When Missing

If StyleCop.Analyzers is not configured yet:

  1. Detect current state:
    • rg -n "StyleCop\\.Analyzers|stylecop\\.json" -g '*.csproj' -g 'stylecop.json' .
  2. Add package to the intended scope:
    • dotnet add PROJECT.csproj package StyleCop.Analyzers
  3. Keep severity in root .editorconfig and use stylecop.json only for StyleCop-specific behavior.
  4. Prevent overlap with existing analyzer packs by defining ownership.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. If the repo intentionally uses SDK analyzers only, return status: not_applicable.

Read the full file on GitHub · 108 lines

Files

What ships with it

4 files 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.

Changes

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.

  1. 19d ago First seen · 108 lines · 51 tokens per session scan A 96765166da6e

Subscribe to this mod's changes

stylecop-analyzers is a skill published in the GitHub repository managedcode/Orleans.RateLimiting (30 stars, last pushed 11d ago), licensed MIT. It adds 51 tokens to every session and 945 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to stylecop-analyzers, differing in 8 lines, and is treated as a copy.

Code reviewdotnetlimiterorleansrate-limiterrate-limiting
Related

Other skills, from other repositories

code-analysis

Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. USE FOR: the repo wants first-party .NET analyzers; CI should fail on analyzer warnings; the team needs AnalysisLevel or AnalysisMode guidance. DO NOT USE FOR: third-party analyzer selection by itself; formatting-only…

managedcode/dotnet-skills · 99 tokens

graphify-dotnet

Use graphify-dotnet to generate codebase knowledge graphs, architecture snapshots, and exportable repository maps from .NET or polyglot source trees, with optional AI-enriched semantic relationships. USE FOR: graphify commands; graph JSON, HTML, SVG, Cypher, Markdown, and Obsidian exports; repository map and…

managedcode/dotnet-skills · 125 tokens

sonarjs

Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. USE FOR: SonarQube, SonarCloud, or eslint-plugin-sonarjs setups; frontend code smells; cognitive complexity and deeper…

managedcode/dotnet-skills · 132 tokens

address-review

Read PR review comments from GitHub, evaluate, address, and reply.

fpindej/netrock · 14 tokens

complexity

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. USE FOR: the team wants to find overly complex methods; cyclomatic complexity thresholds are needed in CI; maintainability metrics or coupling thresholds need to be configured. DO NOT USE…

managedcode/dotnet-skills · 106 tokens

resharper-clt

Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…

managedcode/dotnet-skills · 107 tokens