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.
git clone --depth 1 https://github.com/frankxai/Starlight-Intelligence-SystemWrote 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/commands/frankxai/starlight-intelligence-system/music-amplify)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/music-amplify"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/music-amplify/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/commands/frankxai/starlight-intelligence-system/music-amplify"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/music-amplify.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.00030 | $0.00809 |
| Opus 5 | $0.00015 | $0.00404 |
| Sonnet 5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
music-amplify 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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/music-amplify — Cross-platform amplification scheduling
Schedule cross-platform amplification drops for a released song via the OpenClaws mesh (Claw-X, Claw-IG, Claw-TT, Claw-YT, Claw-SP). Voice-lock-checked, frequency-capped, AI-disclosed.
Usage
/music-amplify frank-riemer_20260501_threshold all
/music-amplify pulse-01_20260520_evening-journal x,ig,tt
/music-amplify aetheria-01_20260615_first-light yt,sp
Arguments
- song-id (required) — released song from catalog
- channels (required) —
allOR comma-list of:x,ig,tt,yt,sp
Behavior
Invokes music-is/amplification-mesh skill (Senior tier, Sonnet 4.6) → music-amplifier agent.
Per-Claw drop generation
For each requested channel, the Claw:
- Pulls voice-lock from
verticals/music-is/labels/<label>/personas/<persona>/social/voice-lock-<platform>.md - Composes drop content per platform (X 280char post + thread; IG Reel caption + slides; TikTok 15-30s vertical + caption; YT Shorts; Spotify Canvas + playlist pitch)
- Voice-lock check (auto-rollback up to 3 attempts; escalates to Frank on persistent fail)
- Frequency-cap check (≤3 drops/day per persona across mesh)
- AI-disclosure check (persona bio carries disclosure on platform)
- Schedule via Blotato + n8n
Default amplification cadence (post-release)
T+0h Spotify Canvas live (auto via /music-release)
T+2h Claw-X drop 1 (release announcement)
T+6h Claw-IG Reel
T+24h Claw-TT vertical
T+48h Claw-YT Short
T+72h Claw-X drop 2 (production angle)
T+1w Claw-IG carousel
T+2w Claw-TT drop 2
T+4w Claw-X drop 3
/music-amplify extends or modifies this default for older catalog re-amplification.
Refusals
- Voice-lock fails 3+ times → escalate
- Frequency cap exceeded → defer to next slot
- AI-disclosure missing from persona bio → refuse, fix bio first
- Engagement-bot pattern → refuse, audit
- Drop without canon-anchoring (orphan amplification) → refuse
- Cross-persona post (one Claw posting for multiple personas) → refuse
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.
- 10d ago First seen · 82 lines · 30 tokens per session scan A 2d2af6f71f73
music-amplify is a command published in the GitHub repository frankxai/Starlight-Intelligence-System (8 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 809 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-08-31.
Other commands, from other repositories
memories
View and manage learned memories.
mpm-session-resume
Load context from paused session.
forget
Delete specific memories.
learn
Add new learning to memory.
gbu-retro
Post-session retrospective — harvest this session's lessons into durable doctrine.
consolidate
Write a compact checkpoint summary of the current frontier.