Borrowing it
Nothing to install: this file belongs to managedcode/PrompterOne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/PrompterOne/main/.codex/skills/dotnet-biome/SKILL.mdgit clone --depth 1 https://github.com/managedcode/PrompterOneWrote 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/managedcode/prompterone/dotnet-biome)<a href="https://agentmods.dev/skills/managedcode/prompterone/dotnet-biome"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-biome/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/managedcode/prompterone/dotnet-biome"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-biome.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.00068 | $0.01161 |
| Opus 5.5 | $0.00027 | $0.00464 |
| Sonnet 5.5 | $0.00014 | $0.00232 |
| Haiku 4.5 | $0.00007 | $0.00116 |
Grade A, and why
dotnet-biome 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 1mo 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.
This is a copy
91% identical to biome — 16 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Biome for Frontend Assets in .NET Repositories
Trigger On
- the repo has
biome.json,@biomejs/biome, or the user asks for a faster all-in-one frontend formatter-linter stack - the repo wants one tool for formatting, linting, and import organization across JS, TS, CSS, JSON, GraphQL, or HTML
- the team is comparing Biome against ESLint plus Prettier or wants to simplify the current stack
Do Not Use For
- repos that rely on ESLint plugins or framework-specific rules Biome does not cover yet
- runtime site audits such as headers, accessibility, and SEO; route that to
dotnet-webhint - cases where a dedicated CSS or HTML tool is still the deliberate owner and no migration is requested
Inputs
- the nearest
AGENTS.md package.jsonbiome.jsonorbiome.jsonc- current ownership across ESLint, Prettier, Stylelint, and import ordering
Workflow
- Decide ownership first:
- Biome as the main formatter and linter
- Biome only for formatting
- Biome in coexistence with ESLint for plugin gaps
- Prefer a repo-local pinned install so CI and developer machines use the same version.
- Generate
biome.jsononly after confirming what the repo wants Biome to own. - Add repeatable scripts to
package.json, for example:biome check .biome check . --write
- Keep file ownership explicit:
- Biome can own formatting, linting, and import sorting
- webhint still owns site-runtime audits
- ESLint may stay for plugin-heavy cases the repo intentionally keeps
- Start migrations with
checkand bounded folders before flipping the whole repo to--write. - Re-run the frontend build and tests after broad formatting or lint-fix passes.
Bootstrap When Missing
- Detect current state:
rg --files -g 'package.json' -g 'biome.json*'rg -n '"@biomejs/biome"|"eslint"|"prettier"|"stylelint"' --glob 'package.json' .
- Prefer a repo-local pinned install:
npm i -D -E @biomejs/biome
- Create config deliberately:
npx @biomejs/biome init
- Add repeatable commands to
AGENTS.mdandpackage.json, then verify with:npx @biomejs/biome check .npx @biomejs/biome check . --write
- Return
status: configuredif Biome is now wired with explicit ownership, orstatus: improvedif the existing setup was tightened. - Return
status: not_applicablewhen the repo intentionally stays on ESLint-centered ownership and no migration or comparison was requested.
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.
- 1mo ago First seen · 104 lines · 68 tokens per session scan A 8e516a4637a6
dotnet-biome is a skill published in the GitHub repository managedcode/PrompterOne (45 stars, last pushed 5mo ago), licensed MIT. It adds 68 tokens to every session and 1,161 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to biome, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…
minimal-apis
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
web-api
Build or maintain controller-based ASP.NET Core APIs when the project needs controller conventions, advanced model binding, validation extensions, OData, JsonPatch, or existing API patterns. USE FOR: working on controller-based APIs in ASP.NET Core; needing controller-specific extensibility or conventions; migrating…
managedcode-communication
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit…
grpc
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime…