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 agentmods add skills/pyros-projects/limitless/suno-packnpx skills add pyros-projects/limitless --skill suno-packgit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/suno-pack)<a href="https://agentmods.dev/skills/pyros-projects/limitless/suno-pack"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/suno-pack.svg" alt="Measured on agentmods" 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 | $0.00245 | $0.05400 |
| Opus 5 | $0.00122 | $0.02700 |
| Sonnet 5 | $0.00049 | $0.01080 |
| Haiku 4.5 | $0.00024 | $0.00540 |
Grade A, and why
suno-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 3d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suno Pack
Turn a track idea into a complete, paste-ready Suno package: a concept document that gives the track a soul, then per-version prompt artifacts that express it — plus the cover pipeline that combines v4.5's prompt obedience with v5.5's audio quality.
Core principle: concept before prompts. A great track is not a pile of genre tags — it is one emotional idea expressed through sound. Write the concept first; derive every prompt from it. The prompts are the expression of the concept, the same way a canvas expresses a design philosophy.
REQUIRED REFERENCES: Read references/suno-v5-5-prompting.md before
writing any prompt — it carries the shared truth: field limits, the canonical
metatag taxonomy, per-version behavior and slider settings, the cover
workflow, and the instrumental anti-vocal-hallucination kit. When v4.5 is
among the requested versions, ALSO read references/suno-v4-5-prompting.md
for the v4.5-specific prompt styles and lore. Before authoring vocal lyrics,
rewriting lyrics, or diagnosing lyric density/flow problems, read
references/lyrics-rhythm-craft.md — it is the lyric beat-map and performance
notation contract. Before ANY execution work (rendering, covers, library,
experiments), read references/pp-cli.md — the verified command truth; for
experiment mode additionally references/experiment-lanes.md. Do not prompt
from memory and do not improvise CLI flags — model behavior, limits, lyrics,
and the CLI surface are all version-specific.
When to Use
- "Make me a track / song / beat about X"
- "I need Suno prompts for ..." / "lyrics for Suno"
- "Instrumental version of this idea"
- Any creative brief — a mood, a scene, a story, a product, a feeling — that should become music.
Not for: composing sheet music, audio post-production advice, or non-Suno generators (adapt the concept phase, but the prompt syntax is Suno-specific).
Arguments
Parse from the invocation text; accept natural-language equivalents.
| Argument | Default | Effect |
|---|---|---|
--versions <v...> |
5.5 4.5 |
which model versions get prompt files (accepts 5.5 5.0 4.5, comma-separated, or "only v5.5", "all versions") |
--no-cover |
cover on | skip the cover/re-render file |
--cover <from> <to> |
oldest→newest requested | override the cover chain endpoints |
--mode experimental [n|list] |
faithful | experiment mode: random lane, lane n, or the lane menu — see references/experiment-lanes.md |
What ships with it
5 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.
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.
- 3d ago First seen · 464 lines · 245 tokens per session scan A db3b2c359066
suno-pack is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 21d ago), licensed MIT. It adds 245 tokens to every session and 5,400 once invoked, about $0.0012 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 skills, from other repositories
expansion-grant-guard
YAML-based delegation grant ledger — issues, validates, and tracks scoped permission grants for sub-agent expansions with token budgets and auto-expiry.
create-skill
Scaffolds and validates new superpowers skills. Use when creating a new skill for this repository.
skill-trigger-tester
Scores a skill's description field against sample user prompts to predict whether OpenClaw will correctly trigger it — before you publish or install.
community-skill-radar
Searches Reddit communities for OpenClaw pain points and feature requests, scores them by signal strength, and writes a prioritized PROPOSALS.md for you to review and act on.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.
memory-dag-compactor
Builds hierarchical summary DAGs from MEMORY.md with depth-aware prompts — leaf summaries preserve detail, higher depths condense to durable arcs, preventing information loss during compaction.