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 zarlor/suno-band-manager --skill suno-band-profile-managergit clone --depth 1 https://github.com/zarlor/suno-band-managerWrote 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/zarlor/suno-band-manager/suno-band-profile-manager)<a href="https://agentmods.dev/skills/zarlor/suno-band-manager/suno-band-profile-manager"><img src="https://agentmods.dev/badge/skills/zarlor/suno-band-manager/suno-band-profile-manager/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/zarlor/suno-band-manager/suno-band-profile-manager"><img src="https://agentmods.dev/badge/skills/zarlor/suno-band-manager/suno-band-profile-manager.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.00050 | $0.04827 |
| Opus 5 | $0.00025 | $0.02413 |
| Sonnet 5 | $0.00010 | $0.00965 |
| Haiku 4.5 | $0.00005 | $0.00483 |
Grade B, and why
suno-band-profile-manager scanned grade B with 1 finding 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 12d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
All in `scripts/`. **Invoke every script via `uv run scripts/<name>.py`** — uv reads each script's PEP 723 inline metadata and auto-provisions its dependencies (e.g. `pyyaml`), so no manual `pip install` is needed. If `u How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Band Profile Manager
Overview
Acts as a music producer's assistant — part creative collaborator, part technical librarian — managing persistent band identity profiles, the sonic equivalent of a brand book, that define genre, vocal character, production style, creative boundaries, language, and songwriter voice for AI-assisted music creation via Suno. Discovery is conversational and outcome-driven, structured YAML checkpoints survive context compaction, and a sibling decision log carries identity across the months-long life of a profile. Other skills (Style Prompt Builder, Lyric Transformer, Feedback Elicitor) draw from these profiles to maintain consistency across songs, so every field is written for those downstream consumers.
Conventions
- Bare paths (e.g.
references/profile-schema.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.
Output locations come from module config: {band_profiles_folder} (resolves to {project-root}/docs/band-profiles) holds profile YAML and its sibling decision log; {songbook_folder} (resolves to {project-root}/docs/songbook) holds per-band songbook entries that the playlist scaffold reads. Per-band playlist YAML lands at {project-root}/docs/{profile-name}-playlist.yaml.
Principles
- The profile serves downstream skills. Every field is read by the Style Prompt Builder, Lyric Transformer, and Feedback Elicitor — write each one for those consumers, not just for the user reading it back. Vague profiles produce vague songs.
- Capture over interrogate. Absorb volunteered information out of order; never force the user back into sequence.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
What ships with it
19 files 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.
- .decision-log.md 15 KB
- bmad-skill-manifest.yaml 12 B
- customize.toml 875 B
- references/profile-schema.md 21 KB
- references/README.md 3.7 KB
- references/tier-features.md 21 KB
- scripts/apply-profile.py 10.0 KB runs code
- scripts/diff-profiles.py 5.2 KB runs code
- scripts/list-profiles.py 6.3 KB runs code
- scripts/scaffold-playlist.py 9.0 KB runs code
- scripts/tests/conftest.py 266 B runs code
- scripts/tests/test-apply-profile.py 5.2 KB runs code
- scripts/tests/test-diff-profiles.py 4.1 KB runs code
- scripts/tests/test-list-profiles.py 6.8 KB runs code
- scripts/tests/test-scaffold-playlist.py 6.4 KB runs code
- scripts/tests/test-tier-features.py 9.3 KB runs code
- scripts/tests/test-validate-profile.py 16 KB runs code
- scripts/tier-features.py 17 KB runs code
- scripts/validate-profile.py 24 KB runs code
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.
- 12d ago First seen · 209 lines · 50 tokens per session scan B c4208550e48a
suno-band-profile-manager is a skill published in the GitHub repository zarlor/suno-band-manager (11 stars, last pushed 29d ago), licensed MIT. It adds 50 tokens to every session and 4,827 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…