agentmods.dev

lyricist

lyricist is a skill for Claude Code from P47Phoenix/Claude-Plugins. It costs 142 tokens per session (3,005 once invoked), scanned A, original, MIT.

A lyric-writing tool for hooks, verses, pre-choruses, bridges, lyric editing, and extending supplied lyrics. It chooses a writing role based on the request and the text provided.

In plain words
What is it for?
Use it to write new song sections, improve existing lyrics, create hooks, or add verses and bridges to a supplied song.
Why use it?
It routes different lyric jobs to focused roles instead of treating writing, editing, and expansion as the same task. It also applies the supplied originality policy.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents.

Part of the music-team plugin — 9 skills shipped together

not rated 2repo 2d ago A scan 142 tokens original MIT

Good fit Use it to write new song sections, improve existing lyrics, create hooks, or add verses and bridges to a supplied song.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/p47phoenix/claude-plugins/lyricist
View source ↗ P47Phoenix/Claude-Plugins
Install

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.

Any agent
npx skills add P47Phoenix/Claude-Plugins --skill lyricist
Clone the repo
git clone --depth 1 https://github.com/P47Phoenix/Claude-Plugins

Made for: Claude Code.

Or install music-team, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for lyricist

README.md
[![agentmods](https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/lyricist/github.svg)](https://agentmods.dev/skills/p47phoenix/claude-plugins/lyricist)
Your own site
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/lyricist"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/lyricist/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.

agentmods 80×15 button for lyricist

Your own site · 80×15
<a href="https://agentmods.dev/skills/p47phoenix/claude-plugins/lyricist"><img src="https://agentmods.dev/badge/skills/p47phoenix/claude-plugins/lyricist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,005 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00142 $0.03005
Opus 5.5 $0.00057 $0.01202
Sonnet 5.5 $0.00028 $0.00601
Haiku 4.5 $0.00014 $0.00300

Measured 2d ago against content hash a55edbb7cc85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

lyricist 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 2d 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.

music-team/skills/lyricist/SKILL.md · 243 lines

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.

Lyricist

Design Principle: Role Context Isolation

Keep lyric craft knowledge out of the main context. Detect the role, read only the matched role manifest, contract, one genre ## Lyric section and the allowed technique files, then spawn a sub-agent that does the writing. The main context receives the finished artifact and a hand-back, never the craft references. Follow references/shared/originality-policy.md in every prompt: paste its fenced clause verbatim under <!-- originality-policy -->.

Phase 1: Role Detection

Detect the role from, in priority order:

  1. Pipeline invocation. A prompt that begins with SKILL: lyricist carries ROLE: and TASK_TYPE:. Honour them exactly and skip detection.
  2. Explicit role mention. "as the hook writer", "just edit it".
  3. Task signals. See the routing table below.
  4. Supplied-text signals. A supplied lyric plus "fix", "tighten", "polish", "second draft" means lyric-editor. A supplied lyric plus "add", "extend", "one more", "more verses", "bridge for my song" means augmenter. No supplied lyric and a request for a title, chorus or hook means hook-writer; a request for verses or bridges to a concept or structure means verse-writer.

If ambiguous, ask one question before proceeding. Do not assume.

Provenance gate (augmenter and lyric-editor on user-supplied text)

These two roles build on text the user supplied, so they REQUIRE provenance in brief.md: user_asserts_original_input: true, or public_domain: true with public_domain_source.

  • In a pipeline, music-brief already checked it. Re-read the brief front-matter; if neither flag is set, return STATUS: BLOCKED.
  • Standalone, ask once: "Is this lyric your own original work, or public domain (name the source)?" Proceed only on a yes.
  • On a no, or any refusal to say, reply with exactly this sentence and write no artifact: I cannot write a parody of, or a song to the tune of or in the exact style of, a named existing song or artist; I would be glad to write an original song on the same theme and in the same genre instead.
  • A supplied text recognised as a well-known existing lyric: stop and report it (originality clause 4). Never edit or extend it.

Read the full file on GitHub · 243 lines

Files

What ships with it

18 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.

Changes

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.

  1. 2d ago First seen · 243 lines · 142 tokens per session scan A a55edbb7cc85

Subscribe to this mod's changes

lyricist is a skill published in the GitHub repository P47Phoenix/Claude-Plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 3,005 once invoked, about $0.0006 per session on Opus 5.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-10-26.

Creative and media
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens