ecosystem-usage

ecosystem-usage is a skill for Claude Code, Codex from nuxt/nuxt.com. It costs 21 tokens per session (1,775 once invoked), scanned A, original, MIT.

An analytics workflow for measuring how Nuxt and Nuxt UI projects are used through MCP, Markdown, curl, and other clients. It queries Vercel Observability, a service that stores application traffic and metrics.

In plain words
What is it for?
Use it to count production requests, inspect MCP traffic, measure raw Markdown consumption, and identify which clients use Nuxt or Nuxt UI. It supports separate queries for the two projects and detailed request filters.
Why use it?
It provides a defined source and query method for answering adoption and traffic questions. Comparing the requested period with the preceding period helps show whether usage changed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex; mentions OpenCode.

Good fit Use it to count production requests, inspect MCP traffic, measure raw Markdown consumption, and identify which clients use Nuxt or Nuxt UI. It supports separate queries for the two projects and detailed request filters.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nuxt/nuxt.com/ecosystem-usage
Install

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.

Any agent
npx skills add nuxt/nuxt.com --skill ecosystem-usage
Clone the repo
git clone --depth 1 https://github.com/nuxt/nuxt.com

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ecosystem-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/nuxt/nuxt.com/ecosystem-usage/github.svg)](https://agentmods.dev/skills/nuxt/nuxt.com/ecosystem-usage)
Your own site
<a href="https://agentmods.dev/skills/nuxt/nuxt.com/ecosystem-usage"><img src="https://agentmods.dev/badge/skills/nuxt/nuxt.com/ecosystem-usage/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.

agentmods 80×15 button for ecosystem-usage

Your own site · 80×15
<a href="https://agentmods.dev/skills/nuxt/nuxt.com/ecosystem-usage"><img src="https://agentmods.dev/badge/skills/nuxt/nuxt.com/ecosystem-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01775
Opus 5 $0.00010 $0.00888
Sonnet 5 $0.00004 $0.00355
Haiku 4.5 $0.00002 $0.00178

Measured yesterday against content hash 5dd602dbf2cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-13, from the pricing page.

Security

Grade A, and why

ecosystem-usage scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Use this skill when an admin asks about MCP adoption, AI-agent traffic, raw Markdown consumption, curl usage, or which clients use Nuxt/Nuxt UI.
layers/nuxi/agent/skills/ecosystem-usage/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use this skill when an admin asks about MCP adoption, AI-agent traffic, raw Markdown consumption, curl usage, or which clients use Nuxt/Nuxt UI.

Source of truth

Use vercel-mcp__search_vercel_endpoints to discover POST /v2/observability/query, then call it through vercel-mcp__call_vercel_endpoint.

  • Metric: vercel.request.count
  • Aggregation: sum
  • Scope:
    • type: project
    • ownerId: the configured Nuxt team id
    • projectIds: one configured project id, Nuxt or Nuxt UI
  • Always filter to environment eq 'production'.
  • Use ISO UTC timestamps for startTime and endTime.
  • Because the Results block includes a change, always query the requested window and the immediately preceding equal-length window with the same scope and filter.

Query recipes

Run independent Nuxt and Nuxt UI queries in parallel. A per-call batch or concurrency limit is not a total-query limit. Continue with additional call_vercel_endpoint batches until every requested total and detail query is complete.

  1. MCP request volume:
    • Filter: request_path eq '/mcp' and environment eq 'production'
    • For Nuxt and Nuxt UI separately, first query the current and previous equal-length windows ungrouped for exact HTTP request counts.
    • For each project, group the current window by client_user_agent (limit 25), bot_category + bot_name (limit 20), and request_method + http_status (limit 20).
  2. Explicit Markdown URLs on each project:
    • Filter: endswith(request_path, '.md') and environment eq 'production'
    • For Nuxt and Nuxt UI separately, query ungrouped, then group by request_path (limit 10) and client_user_agent (limit 10).
  3. Content-negotiated Markdown on each project:
    • Filter: contains(http_accept, 'text/markdown') and environment eq 'production'
    • For Nuxt and Nuxt UI separately, query ungrouped, then group by request_path (limit 10) and client_user_agent (limit 10).
  4. Agent discovery and intake on each project:
    • Filter: (request_path eq '/llms.txt' or request_path eq '/llms-full.txt' or request_path eq '/sitemap.md' or request_path eq '/openapi.json' or request_path eq '/.well-known/mcp/server-card.json') and environment eq 'production'
    • For Nuxt and Nuxt UI separately, query ungrouped, then group by request_path (limit 10), client_user_agent (limit 10), or bot_category + bot_name (limit 10).
    • Keep these separate from content reads: fetching an index or server card does not prove the client consumed a documentation page.
  5. curl traffic, only when explicitly requested:
    • Filter: contains(client_user_agent, 'curl/') and environment eq 'production'
    • Group by request_path and client_user_agent.
    • Exclude asset paths such as /_nuxt/, /_fonts/, and image assets from the interpretation.

Read the full file on GitHub · 95 lines

Changes

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.

  1. yesterday First seen · 95 lines · 21 tokens per session scan A 5dd602dbf2cf

Subscribe to this mod's changes

ecosystem-usage is a skill published in the GitHub repository nuxt/nuxt.com (457 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,775 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.

Related

Other skills, from other repositories

nuxt-ui

Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.

nuxt/ui · 56 tokens

vue-expert

Expert knowledge in Vue.js 3, Composition API, Pinia state management, and Nuxt.js for building modern reactive web applications. Use when the user mentions Vue 3, the Composition API, Pinia, Nuxt, reactive, or frontend, or when the task involves Vue 3 Fundamentals, Composition API, Pinia State Management, or Nuxt.js.

personamanagmentlayer/pcl · 78 tokens

nuxt-docs

Nuxt 4.x — full-stack Vue.js framework. File-based routing, auto-imports, SSR, Nitro, layers, modules.

pledgeandgrow/pledge-skills · 33 tokens

content-pass

The daily pass over evlog's written surfaces. Picks the files the scanner ranks worst across the docs, the landing, the package READMEs, the skills, and the AGENTS.md files, reviews them against the content doctrine, applies what holds, and opens one draft PR whose body is the report. Also covers the enrichment half…

HugoRCD/evlog · 154 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

self-review

Weekly pass over the evlog repository and Evi's own surface, in two halves — what has drifted out of coherence (a capability wired but never consumed, code contradicting a written guide, a description promising a tool the allowlist lacks), and what is missing (a capability worth having, a manual step worth automating…

HugoRCD/evlog · 117 tokens