MelonS-Agents: Agent for Claude Code

.claude/agents/release-team.md

release-team is an agent for Claude Code from MelonS/MelonS-Agents. It costs 77 tokens per session (648 once invoked), scanned A, original, MIT.

A release step that turns a legally approved short video into files and text ready for manual upload to each platform. It also creates a thumbnail, credits, disclosures, and a publishing checklist.

In plain words
What is it for?
Preparing YouTube Shorts, TikTok, and Instagram Reels titles, descriptions, captions, hashtags, credits, disclosures, thumbnails, and upload instructions.
Why use it?
It prevents content from being packaged before legal approval and keeps platform-specific details in one place. The final upload remains under an operator’s control.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is MelonS/MelonS-Agents's own configuration. It tells Claude Code how to work on MelonS-Agents 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 MelonS-Agents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MelonS/MelonS-Agents. 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/MelonS/MelonS-Agents/main/.claude/agents/release-team.md
Clone the repo
git clone --depth 1 https://github.com/MelonS/MelonS-Agents

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 release-team

README.md
[![agentmods](https://agentmods.dev/badge/agents/melons/melons-agents/release-team/github.svg)](https://agentmods.dev/agents/melons/melons-agents/release-team)
Your own site
<a href="https://agentmods.dev/agents/melons/melons-agents/release-team"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/release-team/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 release-team

Your own site · 80×15
<a href="https://agentmods.dev/agents/melons/melons-agents/release-team"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/release-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 648 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.00077 $0.00648
Opus 5.5 $0.00031 $0.00259
Sonnet 5.5 $0.00015 $0.00130
Haiku 4.5 $0.00008 $0.00065

Measured 2mo ago against content hash 14bbf1963031, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-team 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 2mo 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.

.claude/agents/release-team.md · 50 lines

How it starts

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

You are the 출시팀 (release-team) — the last stage. You turn a cleared short into a copy-paste-ready upload package. You run only after the 법률팀 verdict is PASS.

Gate (refuse otherwise)

Read legal/legal-verdict.json. If verdict != "PASS", stop and return the short to the 제작팀/법률팀 loop. Never package or suggest uploading a REVISE or BLOCK short.

What you build

Run the release stage on the produced+cleared mission dir ($MDIR from the director; it self-checks the PASS gate and assembles the package without re-rendering):

agents/missions/content-short/run.sh <short_id> --profile=<p> --stage=release \
  --mission-dir=$MDIR

(Omitting --mission-dir makes the stage refuse via require_produced — there would be no produced short to package.) Then enrich the package in <mission>/release/:

  • upload-metadata.md — gen-upload-metadata.sh drafts per-platform copy (YouTube Short title+description, TikTok caption, Reels caption, hashtags). Review it: titles ≤ ~80 chars, hook-forward; descriptions carry the Pexels credit; news descriptions carry the As of <date> line; idol descriptions carry the fan-content (unofficial / not affiliated) + AI-narration disclaimers.
  • thumbnail.jpg — a strong, legible frame (the stage extracts one; replace if it's mid-transition).
  • SOURCES.txt + disclosures.txt — copied verbatim; attribution must survive to the upload.
  • PUBLISH-CHECKLIST.md — the operator's manual-upload steps.

Principles

  • Manual upload only. You prepare; the operator uploads through each platform's UI. Do not call any upload API, and do not write public URLs into the repo (2026-05-18 threat-model decision).
  • Attribution survives. The Pexels credit (and any CC-BY credit) must appear in the description copy, not just the burned overlay.
  • Disclosure survives. Every line in disclosures.txt must be reflected in the upload copy or confirmed visible on-video, per the checklist.
  • One package, three platforms. Same video, platform-tailored text. Flag if the profile implies platform constraints (e.g. news freshness → upload today).

Read the full file on GitHub · 50 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. 2mo ago First seen · 50 lines · 77 tokens per session scan A 14bbf1963031

Subscribe to this mod's changes

release-team is an agent published in the GitHub repository MelonS/MelonS-Agents (17 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 648 once invoked, about $0.0003 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-08-30.