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 ur-grue/autopunk-media-skills --skill festival-strategy-briefgit clone --depth 1 https://github.com/ur-grue/autopunk-media-skillsWrote 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/ur-grue/autopunk-media-skills/festival-strategy-brief)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/festival-strategy-brief"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/festival-strategy-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.
<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/festival-strategy-brief"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/festival-strategy-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 108 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00037 | $0.01763 |
| Opus 5 | $0.00018 | $0.00881 |
| Sonnet 5 | $0.00007 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
festival-strategy-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 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.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Festival Strategy Brief
What This Skill Does
Produces a festival submission strategy brief for a documentary or short film, identifying target festivals by tier, submission windows, positioning priorities, and a recommended sequencing plan.
When To Use This Skill
- A film is approaching picture lock and the team needs to plan the festival run before submitting anywhere
- A producer or sales agent wants a strategic overview before spending money on submission fees
- A first-time filmmaker needs guidance on which festivals to target and in what order
- A project has already premiered at one festival and needs a second-phase strategy for continued circulation
What You Need To Provide
Required: Film title, format (feature documentary, short documentary, short film), running time, subject/theme in 2–3 sentences, country of production, completion date or expected completion date.
Optional: Existing festival interest or invitations, co-production countries, language and subtitle status, any awards or selection history, preferred geographic markets (European circuit, North American circuit, Asian circuit), sales agent status, broadcast deals already in place.
How the Assistant Approaches This
- Establishes the film's positioning — its genre, subject, and tone — and identifies which festival categories and strands it is most likely to be competitive in (e.g., competitive documentary, human rights, environmental, experimental, short film)
- Proposes a tiered festival list organised by prestige/strategic value: Tier 1 (world premiere, maximum visibility), Tier 2 (regional premiere or strong specialist festival), Tier 3 (broader circuit, audience building, qualification for awards eligibility)
- Outlines submission sequencing advice: which festivals require world premiere status, which accept post-premiere, approximate submission deadlines, and any strategic conflicts to avoid
- After the brief, provides a "Next Step" note: verify the Tier 1 submission deadline immediately on the festival's official website, decide on the world premiere festival before any other submission, and whether to run press-release-writer to prepare the announcement press release before the submission deadline
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 117 lines · 37 tokens per session scan A f9fc902c1d65
festival-strategy-brief is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 12d ago), licensed MIT. It adds 37 tokens to every session and 1,763 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
multi-platform-distribution
Use when one piece of content becomes 10 — blog to Twitter thread, LinkedIn article, YouTube script, newsletter, TikTok script, podcast outline, Reddit post. Use when working with multi platform distribution.
xiaoyuzhou-podcast-notes
A workflow that turns a public Xiaoyuzhou FM podcast episode into structured Markdown notes and a saved transcript. Xiaoyuzhou FM is a Chinese podcast platform.
c-research
Summarize web URLs, PDFs, YouTube videos, and podcasts using the summarize CLI. Instantly extract key points from any content type without manual reading. Useful for research, link digests, and media review.
x-longtail-strategy
A strategy for understanding why most posts on X, formerly known as Twitter, receive ordinary engagement while a small number receive much more. It treats growth as improving the chance of producing posts in the top group rather than expecting every post to go viral.
Distribution Restraints Review
Use when a distribution, dealer, franchise, or marketplace program contains resale-price (RPM/MAP), territory or customer, online-sales, marketplace-ban, dual-pricing, exclusivity, or selective-distribution restraints, to produce a draft restraint inventory with per-jurisdiction character flags, ancillarity notes, and…
Podcast Automation
Automate podcast production workflows including recording, editing, publishing, and distribution.