Borrowing it
Nothing to install: this file belongs to ZapSign/api-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ZapSign/api-mcp/main/.cursor/skills/mcp-growth-metrics/SKILL.mdgit clone --depth 1 https://github.com/ZapSign/api-mcpWrote 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/zapsign/api-mcp/mcp-growth-metrics)<a href="https://agentmods.dev/skills/zapsign/api-mcp/mcp-growth-metrics"><img src="https://agentmods.dev/badge/skills/zapsign/api-mcp/mcp-growth-metrics/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/zapsign/api-mcp/mcp-growth-metrics"><img src="https://agentmods.dev/badge/skills/zapsign/api-mcp/mcp-growth-metrics.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.00643 |
| Opus 5 | $0.00038 | $0.00321 |
| Sonnet 5 | $0.00015 | $0.00129 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
mcp-growth-metrics 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP growth metrics
Canonical sources
- Trends (fixed URL — do not change query set):
https://trends.google.com/trends/explore?geo=BR&q=zapsign%20api,zapsign%20mcp,zapsign%20chatgpt,zapsign%20claude
Geo: Brazil. Default timeframe: Past 12 months. - npm downloads API:
https://api.npmjs.org/downloads/point/{period}/{package}
Packages:mcp-server-zapsign(official),@marcelocorrea/mcp-zapsign(benchmark). - Snapshot store:
docs/marketing/snapshots/YYYY-MM-DD.json - Status log:
docs/marketing/STATUS.md - Official agent hub (always list under presence):
https://agents.zapsign.com.br · https://agents.zapsign.com.br/llms.txt
Take a snapshot
- Run from repo root:
node scripts/marketing/take-snapshot.mjs
(optional date:node scripts/marketing/take-snapshot.mjs 2026-07-21) - Open the Trends URL in the browser. Dismiss cookie banners. Wait until Interest over time and related tables load (Brazil, Past 12 months).
- Read relative interest (0–100) for each term from the chart legend / average interest widgets. Never invent numbers. If blocked or empty, leave
nulland explain intrends.notes. - Update the snapshot JSON
trends.termsand clear or rewritetrends.notes. - Load the previous snapshot (latest earlier
YYYY-MM-DD.json) and compute deltas for npmlast_weekand Trends ranking among the four terms. - Append a short entry (5–10 lines) to
docs/marketing/STATUS.mdwith date, npm WoW delta for the official package, Trends ranking, and any presence changes.
Report format
### YYYY-MM-DD
- npm mcp-server-zapsign: last_week=N (Δ vs prior snapshot)
- npm @marcelocorrea/mcp-zapsign: last_week=N
- Trends BR (past 12 mo): ranking of the four terms + values if known
- Presence notes
- Next focus (one line)
Rules
- Same Trends URL every time (comparability).
- Trends values are relative within the query set — not absolute search volume.
- Do not scrape unofficial Trends APIs; use the browser UI.
- Do not modify product MCP tools for marketing.
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 · 53 lines · 76 tokens per session scan A 9ca232469afa
mcp-growth-metrics is a skill published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 643 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…