agentmods.dev

weekly-brief

weekly-brief is a skill for Claude Code from amplitude/mcp-marketplace. It costs 70 tokens per session (4,784 once invoked), scanned A, original, MIT.

A weekly report from Amplitude, a product-analytics service that tracks how people use software. It compares the past seven days with earlier weeks and summarizes important changes.

In plain words
What is it for?
Preparing a weekly review, finding trends, wins, risks, and turning points, and creating a concise update to share with others.
Why use it?
It saves time spent scanning dashboards and turns scattered usage data into a recap for a team or leadership meeting.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the amplitude plugin — 37 skills shipped together

not rated 35repo +1 3d ago A scan SkillSpector: pass 70 tokens original MIT

Good fit Preparing a weekly review, finding trends, wins, risks, and turning points, and creating a concise update to share with others.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/amplitude/mcp-marketplace/weekly-brief
View source ↗ amplitude/mcp-marketplace
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 amplitude/mcp-marketplace --skill weekly-brief
Clone the repo
git clone --depth 1 https://github.com/amplitude/mcp-marketplace

Made for: Claude Code.

Or install amplitude, the plugin that ships this one along with the rest of its 37 skills.

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 weekly-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/weekly-brief/github.svg)](https://agentmods.dev/skills/amplitude/mcp-marketplace/weekly-brief)
Your own site
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/weekly-brief"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/weekly-brief/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 weekly-brief

Your own site · 80×15
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/weekly-brief"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/weekly-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00070 $0.04784
Opus 5 $0.00035 $0.02392
Sonnet 5 $0.00014 $0.00957
Haiku 4.5 $0.00007 $0.00478

Measured 12d ago against content hash f1b2df85743c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

weekly-brief 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 12d 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.

plugins/amplitude/skills/weekly-brief/SKILL.md · 173 lines

How it starts

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

Amplitude Weekly Insights

You are a proactive analytics advisor that delivers a concise, actionable weekly briefing from a user's Amplitude instance. Your goal is to synthesize the past 7 days into a narrative that highlights the biggest trends, wins, risks, and inflection points — so the user can share it with their team or walk into a Monday meeting fully prepared. This is a weekly brief, not a daily check-in. Focus on week-over-week trends, cumulative momentum, and strategic implications rather than day-by-day noise. Use the prior 4 weeks as a comparison baseline.

Instructions

Phase 1: Understand the User and Their Business

Before scanning data, build context about who you're talking to and what they care about.

  1. Detect persona. Ask or infer the user's role: executive, PM, analyst, growth, or engineering. This determines the language, depth, and framing of the entire briefing.

  2. Bootstrap context (1 call first, then 2 discovery calls in parallel). Start with get_amplitude_context to get user info, projects, recent activity, and key dashboards. Then run two searches in parallel — one for org-wide signal, one for the user's own activity:

    Search A — Org-wide importance. search_amp_entities with isOfficial: true, sortOrder: "viewCount", limitPerQuery: 10. Don't filter by entityTypes — let it return whatever the org's most-viewed official content is (dashboards, charts, notebooks, experiments, etc.). This surfaces what matters to the broader team regardless of whether this specific user has looked at it.

    Search B — User-personalized activity. search_amp_entities with no isOfficial filter, sortOrder: "lastModified", limitPerQuery: 10. Adapt entityTypes based on what get_amplitude_context reveals about the user's recent activity: always include DASHBOARD and CHART as a baseline, then add EXPERIMENT/FLAG if they recently viewed those, NOTEBOOK if they spend time there, COHORT/SAVED_SEGMENT if they work with segments, GUIDE/SURVEY if they use those. When in doubt, omit entityTypes entirely — the API defaults to ["CHART", "DASHBOARD", "NOTEBOOK", "EXPERIMENT"] and personalizes results automatically.

Read the full file on GitHub · 173 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. 12d ago First seen · 173 lines · 70 tokens per session scan A f1b2df85743c

Subscribe to this mod's changes

weekly-brief is a skill published in the GitHub repository amplitude/mcp-marketplace (35 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 4,784 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-08-30.

Analytics and metrics
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens