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/sound-catalog-metadata-pack)<a href="https://agentmods.dev/commands/frankxai/starlight-intelligence-system/sound-catalog-metadata-pack"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/sound-catalog-metadata-pack/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/sound-catalog-metadata-pack"><img src="https://agentmods.dev/badge/commands/frankxai/starlight-intelligence-system/sound-catalog-metadata-pack.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.00055 | $0.00892 |
| Opus 5 | $0.00028 | $0.00446 |
| Sonnet 5 | $0.00011 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
sound-catalog-metadata-pack 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sound-catalog-metadata-pack
Load verticals/sound-intelligence/SKILL.md, agents/starlight-sound-catalog.md, skills/sound-intelligence/catalog-systems.md. Produce a complete Metadata Pack that gates release shipping.
Disclaimer (non-waivable)
Metadata pack is the substrate the catalog runs on. Royalty leakage starts here. This is system architecture, not legal advice.
Process
- Disclaim.
- Per-track field completion (DDEX-aligned where applicable).
- Splits totaling 100% per track.
- Sample clearance status per sample (never blank).
- AI-involvement disclosure per track.
- Sync-availability flag per track tied to vision boundaries.
- Alternate-version mapping per track.
- Discography position per track / release.
- DDEX validation pass.
- Save:
sound-intelligence/catalog/metadata-<release-slug>-<YYYY-MM-DD>.md. - Hand off: distribution submission (actual flow) or master finalization.
Output format
# Metadata Pack — <Release> — <YYYY-MM-DD>
> **Royalty leakage starts here. This is system architecture, not legal advice.**
## Per-track metadata
### Track 1: <Title>
- **ISRC:** XX-XXX-YY-ZZZZZ
- **ISWC:** T-XXXXXXXXX-X
- **Splits (totaling 100%):**
| Contributor | Role | PRO | PRO ID | % |
|---|---|---|---|---|
| ... | composer | ASCAP | XXX | 50 |
| ... | producer | BMI | XXX | 30 |
| ... | featured artist | SESAC | XXX | 20 |
- **Instrumentation tags (DDEX):** <list>
- **Sample clearance:**
| Sample | Source | Status |
|---|---|---|
| ... | ... | cleared / public domain / practitioner-original / pending / refused-uncleared |
- **AI involvement:** <none | disclosed: <description>>
- **Sync-availability flag:** <yes / no / case-by-case> — rationale: <vision-boundary respect>
- **Alternate-version map:**
| Version | ISRC | Diff from main |
|---|---|---|
| instrumental | ... | no vocals |
| sync-grade | ... | PSR ≥ 12 dB master |
- **Language:** <code or instrumental>
- **Explicit:** <yes / no>
- **Genre:** primary / secondary
- **Key:** <musical key>
- **Tempo:** <BPM>
- **Mood tags:** <list — useful for sync brief-fit>
- **Discography position:** <follows X / sets up Y>
### Track 2: ...
[same structure]
## DDEX validation
- Pass: <yes — submitted for distribution | no — fix and resubmit: <list>>
## Refusal-check
- Metadata-as-marketing-only: refused
- Single-track-into-algorithm without discography position: refused
- Sample-clearance blank: refused
**Built on SIP** — SIP v1.1.0 · Sound Intelligence — Catalog · 2026-04-26
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.
- 9d ago First seen · 94 lines · 55 tokens per session scan A ac5c6f7c5417
sound-catalog-metadata-pack is a command published in the GitHub repository frankxai/Starlight-Intelligence-System (8 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 892 once invoked, about $0.0003 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-03.
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.