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 bitwize-music-studio/claude-ai-music-skills --skill promote-ideagit clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skillsWrote 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/bitwize-music-studio/claude-ai-music-skills/promote-idea)<a href="https://agentmods.dev/skills/bitwize-music-studio/claude-ai-music-skills/promote-idea"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/promote-idea/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/bitwize-music-studio/claude-ai-music-skills/promote-idea"><img src="https://agentmods.dev/badge/skills/bitwize-music-studio/claude-ai-music-skills/promote-idea.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.01775 |
| Opus 5 | $0.00025 | $0.00888 |
| Sonnet 5 | $0.00010 | $0.00355 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
promote-idea 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 13d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Task
Input: $ARGUMENTS
Convert a Pending idea from IDEAS.md into a full album project in one
call. Replaces the manual 3-step workflow (get_ideas → new-album →
update_idea) with a single entry point.
Promote Idea Skill
Step 1: Parse Arguments
Expected formats:
"<idea title>"— auto-derive slug from the title"<idea title>" <album-slug>— override the auto-derived slug"<idea title>" documentary— standard slug, documentary flag on"<idea title>" <album-slug> documentary— explicit slug + documentary
Examples:
"Kleine Welt"→ slug auto-derived tokleine-welt"The Great Molasses Flood" molasses-flood documentary"Ängstliche Kätzchen"→ slugangstliche-katzchen(diacritics stripped)
If no arguments are supplied, or the title is empty, list the available pending ideas first and ask which one to promote:
Which idea should I promote?
Pending ideas:
1. Kleine Welt (electronic, Thematic)
2. The Great Molasses Flood (folk, Documentary)
3. Linux Kernel Wars (electronic, Character Study)
Reply with the exact title.
Use get_ideas(status_filter="Pending") to fetch the list.
Step 2: Confirm the Derived Slug
Call get_ideas(status_filter="Pending") (or search(query=idea_title, scope="ideas"))
to confirm the idea exists and show the user what's about to happen.
Compute the slug locally for display only (lowercase, strip diacritics, non-alphanumeric → hyphen). If the result looks odd, offer to override:
About to promote:
Idea: Kleine Welt
Slug: kleine-welt
Genre: electronic
Type: Thematic
Proceed? (Or supply a different slug.)
Skip the confirmation step if the user has already provided an explicit slug — that's the signal they've already thought about it.
Step 3: Ask About Documentary Flag (if not already supplied)
The documentary flag decides whether RESEARCH.md and SOURCES.md are
created. This is not derivable from idea metadata — the idea's "Type"
field can say "Documentary" but that's a separate concept (narrative shape).
Ask once:
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.
- 13d ago First seen · 243 lines · 50 tokens per session scan A 9a05b5517ee2
promote-idea is a skill published in the GitHub repository bitwize-music-studio/claude-ai-music-skills (486 stars, last pushed today), licensed CC0-1.0. It adds 50 tokens to every session and 1,775 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-08-30.
Other skills, from other repositories
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
git-history-analysis
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
fly
Fly one thought to its destination across concurrent agents, on whatever the project and harness already have. Lands only when the user has accounted for every detail, never on an agent's say-so.