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 agentmods add skills/nevaberry/nevaberry-plugins/biome-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill biome-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/biome-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/biome-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/biome-knowledge-patch.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.01985 |
| Opus 5 | $0.00004 | $0.00992 |
| Sonnet 5 | $0.00002 | $0.00397 |
| Haiku 4.5 | $0.00001 | $0.00198 |
Grade A, and why
biome-knowledge-patch 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Biome Knowledge Patch
Use this skill when selecting current Biome configuration, CLI, formatter, analyzer, language, editor, or plugin behavior. Read the reference matching the task before editing configuration or interpreting diagnostics.
Reference map
| Reference | Topics |
|---|---|
| CLI, editors, and reporters | Command selection, reporters, exit behavior, watch mode, daemon logging, LSP, editor actions, JavaScript API |
| Configuration and migration | Configuration discovery and inheritance, monorepos, includes, overrides, VCS ignores, ESLint/Prettier migration |
| Formatting, assists, and suppressions | Formatter settings, import organization, assists, safe/unsafe fixes, suppressions, sorting |
| GritQL search and plugins | Structural search, custom definitions, lint plugins, languages, scoped plugins, rewrites |
| Languages and frameworks | CSS, GraphQL, HTML, SVG, JSON dialects, JSX/TypeScript syntax, React, Vue, Svelte, Astro |
| Linting and project analysis | Domains, module graph and type inference, rule configuration, promotions, new rules, framework-aware analysis |
Work from the effective configuration
- Locate the configuration selected for the working directory or editor workspace.
- Determine whether the file belongs to a nested package configuration.
- Resolve
extends, ordered include patterns, the first matching override, and any editor-only inline configuration. - Determine which language tools, linter domains, individual rules, and assist actions are active.
- Run the narrowest suitable command and inspect its exit status and reporter output.
Handle configuration roots and inheritance
Every configuration is a root unless it explicitly opts out. A nested package
must set "root": false or use "extends": "//"; the latter inherits the
monorepo root and implies root: false.
What ships with it
7 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.
- coverage.json 1.6 KB
- references/cli-editors-and-reporters.md 6.7 KB
- references/configuration-and-migration.md 6.4 KB
- references/formatting-assists-and-suppressions.md 5.7 KB
- references/gritql-search-and-plugins.md 3.1 KB
- references/languages-and-frameworks.md 8.1 KB
- references/linting-and-project-analysis.md 17 KB
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.
- 4d ago First seen · 225 lines · 8 tokens per session scan A 97805093492e
biome-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 8d ago), licensed MIT. It adds 8 tokens to every session and 1,985 once invoked, about $0.0000 per session on Opus 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-08-30.
Other skills, from other repositories
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
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.