Borrowing it
Nothing to install: this file belongs to richardthe3rd/cambridge-beer-festival-app. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/richardthe3rd/cambridge-beer-festival-app/main/.claude/skills/my-festival-campaign/SKILL.mdgit clone --depth 1 https://github.com/richardthe3rd/cambridge-beer-festival-appWrote 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/richardthe3rd/cambridge-beer-festival-app/my-festival-campaign)<a href="https://agentmods.dev/skills/richardthe3rd/cambridge-beer-festival-app/my-festival-campaign"><img src="https://agentmods.dev/badge/skills/richardthe3rd/cambridge-beer-festival-app/my-festival-campaign/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/richardthe3rd/cambridge-beer-festival-app/my-festival-campaign"><img src="https://agentmods.dev/badge/skills/richardthe3rd/cambridge-beer-festival-app/my-festival-campaign.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.00227 | $0.08573 |
| Opus 5 | $0.00113 | $0.04287 |
| Sonnet 5 | $0.00045 | $0.01715 |
| Haiku 4.5 | $0.00023 | $0.00857 |
Grade A, and why
my-festival-campaign scanned grade A 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS https://data.cambeerfestival.app/health How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
My Festival campaign — Phase 1 UI + cloud sync
This is a runbook, not a design doc. Each phase names exact files, gives a baseline command and a verification command, states the observation you should see at the gate, and tells you where to branch if you see something else. Do the phases in order within a track; one PR per phase.
Read as ground truth before starting: docs/planning/my-festival/vision.md
(the product spec) and the proto contract in
proto/cambeerfestival/festival/v1alpha/ (drink_entry.proto,
my_festival_service.proto). Verify any file:line claim below against the code
before you rely on it — the tree moves.
Two independent tracks
- Track A — UI (
#411 → #413 → #414 → #415): local diary. All data stays in SharedPreferences. This is the maintainer's stated hardest live problem and the higher-value track — do it first. - Track B — Sync (D1 + worker + Flutter client): additive backup. Can start
after A1 lands (A1 finalises the local
UserDrinkStateshape that sync serialises). Pervision.mdPhase 3, sync is strictly additive — SharedPreferences stays the source of truth for the UI; the network is a backup, never a read dependency.
Interleaving is fine, but never let Track B change UI behaviour. If a sync PR touches a screen, you have crossed the tracks — split it.
Doc-drift warnings (trust code, not these docs)
docs/planning/rating-service/design.mdis stale. It describes Firebase Anonymous Auth and aRatingsServiceinstorage_service.dart. Neither is real. The deployed worker uses anX-Device-Idheader for identity (no Firebase auth), andRatingsService/FavoritesService/TastingLogServicewere unified intoUserDataStore(lib/services/user_data_store.dart) by #391/#395.storage_service.dartnow holds onlyFestivalStorageService. Use the design doc for intent only; use the proto +cloudflare-worker/+ the code for contract.- AGENTS.md still lists those three deleted services in its Architecture section — same drift, same resolution.
- Deployed API ≠ full proto contract. The proto describes a
DrinkEntryresource (.../entry,drinkEntries) carryingis_favourite,star_rating,would_recommend,note,pours. The worker only implements the narrowerReview(.../review,reviews,reviewSummaries) carryingstarRatingwouldRecommend. TheDrinkEntrysync endpoint is not built — see B3.
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.
- 5d ago Changed · +6 lines 23c5a4334ef4
- 12d ago First seen · 611 lines · 227 tokens per session scan A f9de11113504
my-festival-campaign is a skill published in the GitHub repository richardthe3rd/cambridge-beer-festival-app (2 stars, last pushed yesterday), licensed MIT. It adds 227 tokens to every session and 8,573 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
field-service
Build ServiceNow Field Service Management — wmorder work orders, wmtask tasks, wmresource technicians with skills/territories, dispatch/auto-assignment, mobile status updates, and time entries.
expo-eas-submit
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production…
asc-submission
Prepare an app for App Store submission or TestFlight distribution using the App Store Connect MCP server. Use when user says "prepare submission", "submit to app store", "prepare for review", "update metadata", "set what's new", "check submission readiness", "distribute to testflight", or wants to manage App Store…
gplay-team
Manage a Google Play Developer account's members and their permissions with gplay team. Use when inviting or off-boarding a member, auditing what one member can do, granting or adjusting per-app access, or looking up which permission alias or role bundle to use in the offline team permissions catalog.
app-store-prep
When preparing a release build or responding to rejection reasons.
app-store-launch-orchestrator
Coordinate an Apple app from idea research through specification, design, development, testing, App Store Connect, compliance, review recovery, release, and post-launch measurement. Use when the user asks to create, finish, ship, publish, launch, or assess an iPhone, iPad, macOS, watchOS, tvOS, or visionOS app; when…