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 agentic-community/mcp-gateway-registry --skill usage-reportgit clone --depth 1 https://github.com/agentic-community/mcp-gateway-registryWrote 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/agentic-community/mcp-gateway-registry/usage-report)<a href="https://agentmods.dev/skills/agentic-community/mcp-gateway-registry/usage-report"><img src="https://agentmods.dev/badge/skills/agentic-community/mcp-gateway-registry/usage-report.svg" alt="Measured on agentmods" 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.00038 | $0.12779 |
| Opus 5 | $0.00019 | $0.06390 |
| Sonnet 5 | $0.00008 | $0.02556 |
| Haiku 4.5 | $0.00004 | $0.01278 |
Grade D, and why
usage-report scanned grade D with 2 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 8d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
which pandoc >/dev/null || sudo apt-get install -y pandoc Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
1. **SSH key** at `~/.ssh/id_ed25519` with access to the bastion host How it starts
The opening of the file, as written. The whole thing — 772 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage Report Skill
Export telemetry data from the MCP Gateway Registry's DocumentDB telemetry collector and generate a usage report showing deployment patterns, version adoption, and feature usage in the wild.
Two-pass report generation
Pass 1 (deterministic, Step 7): render_report.py substitutes a fixed template with values pulled directly from the analyzer's JSON/CSV outputs. The Recommendations section is generated by rule-based triggers in recommendations.py. Every number and table cell traces back to a source file. The LLM is not in this path.
Pass 2 (LLM commentary, Step 8): augment_with_commentary.py extracts a manifest of <!-- COMMENTARY:section_id --> markers from the rendered markdown. The skill hands the manifest to the LLM, which produces 2-4 sentence analyst paragraphs per section. The augmenter then substitutes the markers with the commentary text. The LLM only writes prose into pre-defined slots; it cannot modify numbers, tables, or charts.
Together: deterministic data for everything quantitative, LLM voice for synthesis. Hallucination is prevented because the LLM never writes numbers; flat reports are prevented because the commentary layer adds the analyst's interpretation.
To change report content: edit report_template.md (prose, layout, section ordering, commentary anchors), render_report.py (compute new placeholders), recommendations.py (rule-based bullets), or augment_with_commentary.py (commentary marker handling). See Steps 7 and 8 below for full details.
Visualization Guidelines
All charts in this skill follow Edward Tufte's principles documented in tufte-viz-guidelines.md: high data-ink ratio, no chartjunk, layered information, honest scales. The shared style module tufte_style.py provides apply_tufte_style() (rcParams) and tufte_axes(ax) (per-axes cleanup). When adding new chart generators, import from tufte_style and call apply_tufte_style() once before plotting and tufte_axes(ax) for each axes after plotting. Reference the Tufte checklist in tufte-viz-guidelines.md before merging any new chart.
What ships with it
28 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.
- analyze_liveness.py 19 KB runs code
- analyze_telemetry.py 78 KB runs code
- augment_with_commentary.py 8.3 KB runs code
- fetch_github_stats.sh 1.7 KB runs code
- finish_report.sh 2.7 KB runs code
- generate_active_instances_chart.py 13 KB runs code
- generate_adoption_funnel_chart.py 5.7 KB runs code
- generate_charts.py 5.4 KB runs code
- generate_commentary_headless.sh 2.9 KB runs code
- generate_compute_timeseries_chart.py 13 KB runs code
- generate_daily_reporters_chart.py 11 KB runs code
- generate_detection_by_version_chart.py 10 KB runs code
- generate_install_forecast.py 15 KB runs code
- generate_instance_distribution_chart.py 16 KB runs code
- generate_lifetime_buckets_chart.py 10 KB runs code
- generate_lifetime_by_compute_chart.py 15 KB runs code
- generate_lifetime_chart.py 7.6 KB runs code
- generate_ltv_spend.py 38 KB runs code
- generate_prod_internal_chart.py 15 KB runs code
- generate_timeseries_chart.py 12 KB runs code
- recommendations.py 13 KB runs code
- render_report.py 49 KB runs code
- report_template.md 15 KB
- report-style.css 2.9 KB
- run_report_headless.sh 1.9 KB runs code
- run_report.sh 14 KB runs code
- tufte_style.py 4.3 KB runs code
- tufte-viz-guidelines.md 2.8 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.
- 8d ago First seen · 772 lines · 38 tokens per session scan D b99b112509e9
usage-report is a skill published in the GitHub repository agentic-community/mcp-gateway-registry (899 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 12,779 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.