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 roedyrustam/vibes-plug --skill biome-linter-formatter-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/biome-linter-formatter-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/biome-linter-formatter-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/biome-linter-formatter-expert/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/roedyrustam/vibes-plug/biome-linter-formatter-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/biome-linter-formatter-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 49 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 50 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00064 | $0.00785 |
| Opus 5 | $0.00032 | $0.00392 |
| Sonnet 5 | $0.00013 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
biome-linter-formatter-expert 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 11d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Biome Linter & Formatter Expert (2026 Edition)
English
Orchestration & Integration
monorepo-architect: Biome configuration in monorepo workspaces.ci-cd-devops-architect: Biome in CI/CD pipelines.scalability-clean-code: Code quality standards enforcement.typescript-expert: TypeScript-specific lint rules.
Description
Expert guide for Biome v2, the Rust-based unified linter and formatter replacing ESLint + Prettier. Covers migration from ESLint/Prettier, custom rule configuration, CI integration, monorepo setup, and editor integration. Includes performance comparison and best practices for 2026 JavaScript/TypeScript projects.
Trigger Conditions
- Setting up code linting and formatting for new projects.
- Migrating from ESLint + Prettier to Biome.
- Configuring Biome in monorepo or CI/CD pipelines.
- Resolving linting or formatting configuration issues.
Why Biome over ESLint + Prettier?
| Aspect | Biome v2 | ESLint 9 + Prettier 3 |
|---|---|---|
| Speed | 10-100x faster (Rust) | Baseline (Node.js) |
| Config Files | 1 (biome.json) |
2-3 files |
| Formatter + Linter | ✅ Unified | Separate tools |
| Import Sorting | ✅ Built-in | Plugin required |
| CSS/JSON Support | ✅ Built-in | Plugin required |
# Install and init
npm install --save-dev @biomejs/biome
npx biome init
# Migrate from ESLint/Prettier
npx biome migrate eslint --write
npx biome migrate prettier --write
// biome.json
{
"$schema": "https://biomejs.dev/schemas/2.0.0/schema.json",
"organizeImports": { "enabled": true },
"linter": {
"enabled": true,
"rules": {
"recommended": true,
"complexity": { "noExcessiveCognitiveComplexity": "warn" },
"suspicious": { "noExplicitAny": "error" }
}
},
"formatter": {
"enabled": true,
"indentStyle": "space",
"indentWidth": 2,
"lineWidth": 100
}
}
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.
- 11d ago First seen · 90 lines · 64 tokens per session scan A 37d56867018b
biome-linter-formatter-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (50 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 785 once invoked, about $0.0003 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
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
update-dependencies
Upgrade project dependencies with breaking change research for major version updates. Use when the user asks to "update dependencies", "upgrade packages", "upgrade dependencies", "update deps", "upgrade deps", "update npm deps", "update Swift packages", "cargo update", "go get updates", "bundle update", or "pip…
review-plan
Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.
finalize
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
ai-cold-outreach
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,'…