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.
/plugin marketplace add JOYLINK-LTD/lacuna-pluginnpx agentmods add plugins/joylink-ltd/lacuna-plugin/lacuna-plugingit clone --depth 1 https://github.com/JOYLINK-LTD/lacuna-pluginGrade A, and why
lacuna-music 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 yesterday.
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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "lacuna-music",
"displayName": "Lacuna Music",
"version": "1.0.0",
"description": "Generate original AI music from a prompt or your own lyrics — full songs with vocals, instrumentals, and separated stems — through Lacuna's hosted MCP server.",
"author": {
"name": "JOYLINK LTD",
"email": "[email protected]",
"url": "https://www.lacuna.fm/about"
},
"homepage": "https://www.lacuna.fm/ai-song-generator",
"repository": "https://github.com/JOYLINK-LTD/lacuna-plugin",
"license": "MIT",
"keywords": [
"lacuna",
"ai-music",
"music-generation",
"ai-song-generator",
"ai-lyrics-generator",
"stem-separation",
"mcp",
"audio",
"songwriting"
],
"mcpServers": {
"lacuna": {
"command": "npx",
"args": ["-y", "[email protected]"]
}
}
}
What ships with it
1 file beside plugin.json 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.
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.
- yesterday First seen · 33 lines scan A af87f4543ed4
lacuna-music is a plugin published in the GitHub repository JOYLINK-LTD/lacuna-plugin (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-music
AI music production suite using ACE-Step 1.5 via direct Python API. Song generation, cover/style transfer, section editing (repaint), track extraction, multi-track layering, audio completion, songwriting, analysis, platform export, enhancement, and LoRA training. 50+ languages, 10-minute compositions, 48kHz stereo.
runapi
RunAPI model discovery, pricing lookup, media task creation, polling, and balance checks for Claude Code.
pixellab-pip
Routes PixelLab asset/API requests across MCP, REST v2, website/editor workflows, Aseprite, Pixelorama, and legacy v1.
omnimodal
Omnimodal plugin for Claude Code: recognize and generate images, video, and audio through Qwen, Z.AI, or OpenAI-compatible APIs.
ghost-font-decoder
Reveal text hidden in ghost-font videos (motion-defined dot text) using optical flow and OCR.
ai-music-mcp marketplace
Plugin marketplace listing 1 plugin: ai-music-mcp.