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 pantheon-org/tekhne --skill biome-integrationgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/biome-integration)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/biome-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/biome-integration/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/pantheon-org/tekhne/biome-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/biome-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 43 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.00063 | $0.01082 |
| Opus 5 | $0.00032 | $0.00541 |
| Sonnet 5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
nx-biome-integration 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 9d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Biome Integration
Navigation hub for integrating Biome in Nx workspaces with predictable setup and migration.
When to Use
- You need to add Biome lint and format targets in an Nx workspace.
- You are migrating from ESLint or Prettier to Biome.
- You need Nx cache-friendly Biome task configuration.
- You are creating plugin-based inferred tasks for workspace scale.
Principles
- Prefer one root config unless migration constraints require nested overrides.
- Keep lint and format authority singular for each file path.
- Optimize for deterministic CI (read-only checks) and reproducible local fixes.
When Not to Use
- The repository standard is intentionally ESLint/Prettier-only.
- The task is not Nx-related and does not require workspace task integration.
Workflow
- Confirm prerequisites: Nx workspace, Node.js 18+, package manager selected.
- Install Biome and initialize root configuration.
- Add project targets (or plugin inferred tasks) and enable Nx caching inputs.
- Validate lint and format execution on one project, then run across workspace.
- Apply migration strategy (all-at-once or selective nested
biome.json). - Enforce anti-pattern checks before rollout.
Quick Commands
Install and Initialize
npm install --save-dev @biomejs/biome
npx @biomejs/biome init
Expected: root biome.json exists.
Run on One Project
nx biome-lint my-project
nx biome-format my-project
Expected: lint and format targets execute for the selected project.
Run Across Workspace
nx run-many -t biome-lint
nx run-many -t biome-format
Expected: all configured projects run with consistent config and cache behavior.
Run Through Package Script
bun run nx run-many -t biome-lint
Expected: Biome lint runs through package-managed Nx entrypoint.
Reset Nx State After Plugin Changes
nx reset
Expected: daemon cache is cleared and targets refresh.
Anti-Patterns
NEVER use nested biome.json for simple workspace-wide setups
What ships with it
22 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.
- .audits/2026-02-21/analysis.md 8.2 KB
- .audits/2026-02-21/audit.json 145 B
- .audits/2026-02-21/remediation-plan.md 236 B
- .audits/2026-02-22/analysis.md 8.2 KB
- .audits/2026-02-22/audit.json 145 B
- .audits/2026-02-22/remediation-plan.md 236 B
- .audits/2026-02-23/analysis.md 8.2 KB
- .audits/2026-02-23/audit.json 147 B
- .audits/2026-02-23/remediation-plan.md 232 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 419 B
- .audits/2026-03-02/remediation-plan.md 2.2 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 408 B
- CHANGELOG.md 736 B
- evals/scenario-01.md 1.7 KB
- evals/scenario-02.md 2.7 KB
- evals/scenario-03.md 2.8 KB
- evals/scenario-04.md 2.8 KB
- references/biome-configuration-deep-dive.md 2.1 KB
- references/migration-guide.md 2.0 KB
- references/plugin-patterns.md 11 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.
- 9d ago First seen · 136 lines · 63 tokens per session scan A e7a7c0cd735b
nx-biome-integration is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,082 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-09-03.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
atlas-obscura
Search Atlas Obscura for weird, wonderful, and hidden gem places near any destination. Find the interesting stuff, not boring plaques. Search by coordinates, get full details with descriptions and images.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
cf-validate
A validator for 1C configuration source files. It checks the XML structure and the files and objects that make up a 1C business-application configuration.