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 BoxLab-Ltd/yandex-metrica-mcp --skill weekly-reportgit clone --depth 1 https://github.com/BoxLab-Ltd/yandex-metrica-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/boxlab-ltd/yandex-metrica-mcp/weekly-report)<a href="https://agentmods.dev/skills/boxlab-ltd/yandex-metrica-mcp/weekly-report"><img src="https://agentmods.dev/badge/skills/boxlab-ltd/yandex-metrica-mcp/weekly-report/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/boxlab-ltd/yandex-metrica-mcp/weekly-report"><img src="https://agentmods.dev/badge/skills/boxlab-ltd/yandex-metrica-mcp/weekly-report.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.00088 | $0.00920 |
| Opus 5.5 | $0.00035 | $0.00368 |
| Sonnet 5.5 | $0.00018 | $0.00184 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
weekly-report 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 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly report
A weekly report is read in a minute and acted on rarely. Its job is to say whether anything happened, not to fill a page: most weeks the honest headline is "stable". Keep it to one screen.
Sources
Metrica tools are required. Webmaster tools are optional: without them, write
the Metrica part and one line saying search data (pages in search,
diagnostics, Yandex clicks) was not available. If a metrica-hygiene or
webmaster-audit skill is available, its rules apply.
Collect
- Weeks. B = the last full Monday–Sunday week (or the week the user names), A = the week before. Never include today.
- Counter and goals.
describe_counterwithinclude: ["settings", "goals"]. Use the owner's explicit goals (actionandurltypes); skip auto-goals ("Автоцель: …") and "any goal" metrics. - Headline.
run_comparison, A vs B,filtersA/filtersB=ym:s:isRobot=='No', metricsym:s:visits,ym:s:users,ym:s:bounceRateandym:s:goal<id>reachesfor up to three key goals. Take users from this query's totals — never sum days or rows. - Movers. The same comparison by
ym:s:lastsignTrafficSource, then byym:s:startURLPath(limit~20). Keep only rows that pass the noise bar below. - Search (Webmaster). For the main host:
get_hostswithhostId(pages in search, SQI),get_diagnostics(active problems — note any that started during week B),get_indexingreport: "search_events"for week B (appeared / removed),search_queriesreport: "trend"for both weeks (shows, clicks). Note the latest data date of each; if it ends before week B, say "no Webmaster data for this week" instead of reporting it.
Noise bar
Call a change notable only if it is at least 10% and at least ~50 visits (for goals: at least 10% and 10 conversions). Below that it is "flat" or "about the same" — even if the percentage looks big on a small base (a source going 20 → 32 is +60% and still nothing). Do not round notable changes into drama either: say the number.
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.
- yesterday First seen · 73 lines · 88 tokens per session scan A 29044754dab4
weekly-report is a skill published in the GitHub repository BoxLab-Ltd/yandex-metrica-mcp (15 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 920 once invoked, about $0.0004 per session on Opus 5.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-11-06.
weekly-report compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| weekly-reportBoxLab-Ltd/yandex-metrica-mcp | Skill | 15 | yesterday | MIT | A | 88 | Claude Code |
| 21st-ui21st-dev/magic-mcp | Skill | 6.4k | 1mo ago | ISC | A | 63 | Claude Code |
| testrail-qauarlouski/testrail-mcp-server | Skill | 44 | 4d ago | Apache-2.0 | A | 70 | Claude Code, Codex |
| usage-reportergetpapi/papi | Skill | 11 | yesterday | MIT | A | 57 | Claude Code |
| slack-send-safelyjtalk22/slack-mcp-server | Skill | 32 | 3d ago | MIT | A | 65 | Claude Code, Codex |
| papi-buildgetpapi/papi | Skill | 11 | yesterday | MIT | A | 26 | Claude Code |
| deployment-completeness-auditgetpapi/papi | Skill | 11 | yesterday | MIT | A | 44 | Claude Code |