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/usrrname/cursorrules/biomenpx skills add usrrname/cursorrules --skill biomegit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.00013 | $0.00566 |
| Opus 5 | $0.00006 | $0.00283 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
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 2d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Biome Skill
Configure and use Biome for fast JavaScript/TypeScript linting and formatting.
When to Use
- Setting up Biome in a project
- Migrating from ESLint/Prettier to Biome
- Configuring lint rules
- Formatting code with Biome
Critical Rules
Adopt Existing Conventions
If biome.json or biome.jsonc exists in the project:
- Read and adopt the existing configuration
- Do not modify existing rules without explicit request
- Follow the established formatting style (indent, line width, etc.)
- Respect any disabled rules or custom overrides
- Use the project's Biome version specified in package.json
Configuration
- Use
biome.jsonorbiome.jsoncfor configuration - Extend recommended rules as base
- Configure formatter and linter together
- Set up import organization
Performance
- Biome is 10-100x faster than ESLint/Prettier
- Use for CI/CD pipelines
- Format on save in editor
- Run checks in pre-commit hooks
Migration
- Start with
biome migratefrom ESLint/Prettier configs - Disable conflicting rules gradually
- Maintain parity during transition
- Remove old configs after migration complete
Best Practices
- Enable all recommended rules by default
- Use
biome checkfor lint + format in CI - Configure import sorting
- Set up editor integration
Examples
biome.json
{
"$schema": "https://biomejs.dev/schemas/1.5.3/schema.json",
"organizeImports": {
"enabled": true
},
"linter": {
"enabled": true,
"rules": {
"recommended": true,
"correctness": {
"noUnusedVariables": "error"
}
}
},
"formatter": {
"enabled": true,
"indentStyle": "space",
"indentWidth": 2,
"lineWidth": 80
}
}
Commands
# Check lint and format
biome check .
# Check with auto-fix
biome check --apply .
# Format only
biome format --write .
# Lint only
biome lint --apply .
Related
/typescript- TypeScript best practices/react- React patterns that Biome enforces
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.
- 2d ago First seen · 101 lines · 13 tokens per session scan A e3848f00a8cf
biome is a skill published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 13 tokens to every session and 566 once invoked, about $0.0001 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-31.
Other skills, from other repositories
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
sourcery-pr-cycle
Runs the PR creation and Sourcery AI review loop until merge-ready: open PR with gh, poll checks and comments, fix blocking issues, push, re-request review, repeat. Use when the user asks to create a PR, run the Sourcery cycle, address Sourcery review comments, or get a branch merge-ready after review.
feature-development
Feature development workflow for Telegram MCP projects. Use when implementing new features including research, planning, implementation, testing, and documentation.
telegram-patterns
Telegram-specific patterns and Telethon library usage.
typescript-type-safety
Use when encountering TypeScript any types, type errors, or lax type checking - eliminates type holes and enforces strict type safety through proper interfaces, type guards, and module augmentation.
Clean Up Docs Push
Code cleanup, docs update, and git push workflow.