froggo-mission-control: Skill for Claude Code

.claude/skills/froggo-testing-patterns/SKILL.md

mission-control-testing-patterns is a skill for Claude Code from ProfFroggo/froggo-mission-control. It costs 15 tokens per session (718 once invoked), scanned A, original, Apache-2.0.

Testing patterns and setup for the Mission Control platform.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/skills/froggo-testing-patterns/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

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 mission-control-testing-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/froggo-testing-patterns/github.svg)](https://agentmods.dev/skills/proffroggo/froggo-mission-control/froggo-testing-patterns)
Your own site
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/froggo-testing-patterns"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/froggo-testing-patterns/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 mission-control-testing-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/froggo-testing-patterns"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/froggo-testing-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 718 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.
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.00015 $0.00718
Opus 5.5 $0.00006 $0.00287
Sonnet 5.5 $0.00003 $0.00144
Haiku 4.5 $0.00002 $0.00072

Measured today against content hash 359a861ac28e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mission-control-testing-patterns 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 today.

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.

.claude/skills/froggo-testing-patterns/SKILL.md · 66 lines

How it starts

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

Mission Control Testing Patterns

Stack

  • Unit tests: Vitest (npm test or npx vitest run)
  • Type check: npx tsc --noEmit
  • Build check: npm run build:verify (outputs to .next-verify/ — safe for running dev server)
  • Dev server: npm run dev → http://localhost:3000

API Route Testing Pattern

import { GET, POST } from '@/app/api/tasks/route';
import { NextRequest } from 'next/server';

test('GET /api/tasks returns array', async () => {
  const req = new NextRequest('http://localhost/api/tasks');
  const res = await GET(req);
  const data = await res.json();
  expect(Array.isArray(data)).toBe(true);
});

better-sqlite3 in Tests

  • better-sqlite3 is a native module that requires a real SQLite file — it cannot be fully mocked
  • In tests that exercise DB code, use the actual DB at ~/mission-control/data/mission-control.db or a test fixture DB
  • Wrap DB calls in try/catch so tests degrade gracefully if the DB is absent in CI
  • Do NOT mock getDb() with an empty object — the synchronous API calls will throw

Performance Testing (Lighthouse / Core Web Vitals)

CRITICAL: Lighthouse must always target the production build — never the dev server.

Turbopack's dev-mode chunks inflate JS bundle sizes and produce artificially POOR Core Web Vitals readings. A Lighthouse audit against npm run dev is meaningless for performance work.

Correct workflow

# 1. Build for production (outputs to .next-verify/ — safe, does NOT crash the running dev server)
npm run build:verify

# 2. Serve the production build
npx serve .next-verify -p 3005    # or whatever port you choose

# 3. Run Lighthouse against the production build
npx lighthouse http://localhost:3005 --view

Why port 3005 / .next-verify?

  • npm run build:verify writes to .next-verify/ (not .next/), keeping the running dev server untouched.
  • The dev server runs on port 3000. Use a different port (e.g. 3005) for the production-build server to avoid collision.
  • Never run npm run build (no :verify suffix) — it wipes .next/ and crashes the dev server for all users.

Read the full file on GitHub · 66 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. today First seen · 66 lines · 15 tokens per session scan A 359a861ac28e

Subscribe to this mod's changes

mission-control-testing-patterns is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 718 once invoked, about $0.0001 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-07.

Related

mission-control-testing-patterns compared with skills from other repositories

mission-control-testing-patterns next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mission-control-testing-patternsProfFroggo/froggo-mission-controlSkill26mo agoApache-2.0A15Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code