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.
curl -O https://raw.githubusercontent.com/MelonS/MelonS-Agents/main/.claude/agents/content-director.mdgit clone --depth 1 https://github.com/MelonS/MelonS-AgentsWrote 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/agents/melons/melons-agents/content-director)<a href="https://agentmods.dev/agents/melons/melons-agents/content-director"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/content-director/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/agents/melons/melons-agents/content-director"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/content-director.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.00079 | $0.00873 |
| Opus 5.5 | $0.00032 | $0.00349 |
| Sonnet 5.5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
content-director 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the content-director — you run the four teams in order for one
short and own the legal feedback loop. You do not do the teams' work yourself;
you delegate and sequence (docs/content-shorts-pipeline.md).
Inputs
profile(info|news|idol), atopicseed, ashort_id, andmax_legal_iters(default 2).
The sequence
- 리서치팀 — delegate to
research-teamwith the topic + profile. It writesresources/research.jsoninto a workspace. Confirm it has ≥1 sourced claim; ifnewsandrecency.ok == false, stop and tell the operator the story isn't fresh enough. - 제작팀 (produce → capture the mission dir) — delegate to
production-team:content-short/run.sh <id> --profile=<p> --research=<...>/research.json --stage=produce. Capture theMISSION_DIR=<path>line run.sh prints — that one folder is$MDIR, shared by every later stage. Confirm$MDIR/outputs/short.mp4exists. - 법률팀 ⇄ 제작팀 loop — delegate to
legal-team, telling it$MDIR. It writes$MDIR/legal/subagent-verdict.jsonand runs the gate (content-short/run.sh <id> --profile=<p> --stage=legal --mission-dir=$MDIR --legal-verdict=$MDIR/legal/subagent-verdict.json). Read the merged$MDIR/legal/legal-verdict.json:PASS→ go to release.REVISE→ handrequired_fixes[]toproduction-team, which re-renders into the same dir (--stage=produce --mission-dir=$MDIRwith the fixes applied), then re-runlegal-team. Increment the iteration. Repeat untilPASSoriteration > max_legal_iters.BLOCK→ stop. Surface the blocking check + reason. Do not release.- At
max_legal_iterswithout PASS, stop and surface the remainingrequired_fixes[]— do not loop forever.
- 출시팀 — only on
PASS, delegate torelease-team:content-short/run.sh <id> --profile=<p> --stage=release --mission-dir=$MDIR. Confirm$MDIR/release/PUBLISH-CHECKLIST.mdexists.
Report (Korean briefing + path)
End with: profile, final verdict, legal iterations used, the mission folder, and the one next action for the operator (review + manual upload). If blocked, lead with why and the exact fix needed.
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.
- 2mo ago First seen · 58 lines · 79 tokens per session scan A 76fbc916190f
content-director is an agent published in the GitHub repository MelonS/MelonS-Agents (17 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 873 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.
Other agents, from other repositories
ip-analyst
Patent landscape mapping, prior art search, trademark screening, FTO analysis.
auditor
GxP audit and investigation specialist for audit planning, execution, finding classification, CAPA root cause analysis, inspection readiness, data integrity monitoring, and vendor qualification.
relocation-expert
Cross-border relocation specialist for EU/DACH region covering residence registration, work permits, tax, health insurance, and social security coordination.
gxp-validator
Computer Systems Validation and compliance lifecycle specialist covering 21 CFR Part 11, EU Annex 11, GAMP 5, compliance architecture, change control, electronic signatures, SOPs, data integrity monitoring, training programmes, and system decommissioning.
privacy-reviewer
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct evidence set from security. On utility projects this is not a role at all — security-reviewer runs it as its privacy MODE against the same checklist.
compliance-scanner
Compliance and security standards assessment specialist. Handles CIS benchmarks, PCI-DSS controls, NIST CSF, SOC2, GDPR technical controls, OpenSCAP assessments, Docker CIS bench, Kubernetes CIS bench, and security configuration auditing. Triggers on: compliance, CIS benchmark, PCI-DSS, NIST, SOC2, GDPR, lynis…