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 corewebvitals/cwv-superpowers --skill setting-up-coredashgit clone --depth 1 https://github.com/corewebvitals/cwv-superpowersWrote 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/corewebvitals/cwv-superpowers/setting-up-coredash)<a href="https://agentmods.dev/skills/corewebvitals/cwv-superpowers/setting-up-coredash"><img src="https://agentmods.dev/badge/skills/corewebvitals/cwv-superpowers/setting-up-coredash.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.00108 | $0.02077 |
| Opus 5 | $0.00054 | $0.01038 |
| Sonnet 5 | $0.00022 | $0.00415 |
| Haiku 4.5 | $0.00011 | $0.00208 |
Grade B, and why
setting-up-coredash scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Add to `~/.gemini/settings.json`: How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setting Up CoreDash
Invocation
Called by the cwv-superpower orchestrator when CoreDash is unavailable and the user wants to connect, or invoked directly when the user asks how to set up CoreDash MCP.
Do not skip steps. Walk the user through each step and wait for confirmation before moving to the next.
Step 1: Detect the MCP client
Ask the user which tool they are working in:
"Which AI coding tool are you using?"
- Claude Desktop
- Claude Code (terminal)
- Cursor
- Windsurf
- Gemini CLI
- Other
Store the answer for Step 4.
Step 2: Check for a CoreDash account
Ask the user:
"Do you have a CoreDash account at app.coredash.app?"
- If yes: proceed to Step 3.
- If no: say the following and wait:
"You'll need a free CoreDash account first. Go to https://coredash.app/signup and create one. It takes about two minutes. Come back here when you're in."
Step 3: Choose a connection method
CoreDash MCP accepts two authentication methods. Pick based on the client and use case:
| Method | Best for | API key needed? |
|---|---|---|
| Browser login (OAuth) | Interactive use in native/CLI clients like Claude Code (terminal) | No |
API key (cdk_…) |
Headless / automated / CI, agency or multi-project setups (master keys), and config-file clients (Claude Desktop, Cursor, Windsurf, Gemini CLI) | Yes |
Both connect to the same hosted server — nothing changes on the CoreDash side. OAuth is the better experience for interactive clients; API keys are the right choice when there's no interactive browser.
- If the user is on Claude Code (terminal) and wants the simplest path → use Option A (Browser login) in Step 4.
- For headless/CI use, multi-project agency setups, or any config-file client → use Option B (API key) in Step 4.
Step 4: Connect
Option A — Browser login (OAuth), recommended for Claude Code
No API key required. Add the server with no header:
claude mcp add --transport http coredash https://app.coredash.app/api/mcp
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 · 219 lines · 108 tokens per session scan B 0061b346737a
setting-up-coredash is a skill published in the GitHub repository corewebvitals/cwv-superpowers (12 stars, last pushed 2mo ago), licensed MIT. It adds 108 tokens to every session and 2,077 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…