composing-with-pytheory

composing-with-pytheory is a skill for Claude Code from kennethreitz/pytheory-skill. It costs 138 tokens per session (4,618 once invoked), scanned A, a copy of composing-with-pytheory, MIT.

A Python music-composition tool for building chord progressions, melodies, basslines, drum parts, and complete arrangements. It can render the result as audio or MIDI, a format that music software can edit.

In plain words
What is it for?
Use it to sketch songs, generate musical loops, arrange multiple parts, play them, save WAV audio, or export MIDI.
Why use it?
It lets you create repeatable music from a Python script without samples, extra sound plugins, or a digital audio workstation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the composing-with-pytheory plugin — 6 skills shipped together

Good fit Use it to sketch songs, generate musical loops, arrange multiple parts, play them, save WAV audio, or export MIDI.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kennethreitz/pytheory-skill/composing-with-pytheory
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 kennethreitz/pytheory-skill --skill composing-with-pytheory
Clone the repo
git clone --depth 1 https://github.com/kennethreitz/pytheory-skill

Made for: Claude Code.

Or install composing-with-pytheory, the plugin that ships this one along with the rest of its 6 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 composing-with-pytheory

README.md
[![agentmods](https://agentmods.dev/badge/skills/kennethreitz/pytheory-skill/composing-with-pytheory/github.svg)](https://agentmods.dev/skills/kennethreitz/pytheory-skill/composing-with-pytheory)
Your own site
<a href="https://agentmods.dev/skills/kennethreitz/pytheory-skill/composing-with-pytheory"><img src="https://agentmods.dev/badge/skills/kennethreitz/pytheory-skill/composing-with-pytheory/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 composing-with-pytheory

Your own site · 80×15
<a href="https://agentmods.dev/skills/kennethreitz/pytheory-skill/composing-with-pytheory"><img src="https://agentmods.dev/badge/skills/kennethreitz/pytheory-skill/composing-with-pytheory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 138 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,618 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 100% copy Near-identical to another mod 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.00138 $0.04618
Opus 5.5 $0.00055 $0.01847
Sonnet 5.5 $0.00028 $0.00924
Haiku 4.5 $0.00014 $0.00462

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

Security

Grade A, and why

composing-with-pytheory 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 1mo 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.

Origin

This is a copy

100% identical to composing-with-pytheory — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/composing-with-pytheory/skills/composing-with-pytheory/SKILL.md · 330 lines

How it starts

The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Composing with PyTheory

PyTheory turns music theory into runnable Python. You build a Score, add parts (chords, melodies, basslines) and drums, then render it to audio or MIDI — every sound is synthesized from math, so there are no samples, plugins, or DAW to install.

How to work

  1. Write a short Python script that builds a Score and either plays it or saves it. Don't compose by chaining shell one-liners — a script is clearer, reproducible, and easy to iterate on.
  2. Run it with uv run python song.py when uv is available, otherwise python3 song.py.
  3. To let the user hear it, call play_score(score) (speakers) or render to a WAV they can open. To hand off to a DAW, save MIDI.

If PyTheory isn't installed, prefer uv when available: uv pip install pytheory (or uv add pytheory in a uv project); otherwise pip install pytheory. For live MIDI input add the extra: uv pip install "pytheory[live]" (or pip install "pytheory[live]"). NumPy/SciPy ship as PyTheory dependencies, so the scipy.io.wavfile WAV export below needs no extra install.

Core building blocks

from pytheory import Score, Key, Chord, Duration

score = Score("4/4", bpm=120)          # time signature + tempo

# A part is a voice with its own synth/instrument and effects.
piano = score.part("piano", instrument="piano", reverb=0.3)
lead  = score.part("lead", synth="saw", envelope="pluck", lowpass=4000)
bass  = score.part("bass", synth="triangle", lowpass=900)

# Chords from a Key's progression (Roman numerals) or Chord.from_symbol.
for chord in Key("G", "major").progression("I", "V", "vi", "IV"):
    piano.add(chord, Duration.WHOLE)

# Melodies are note names + durations (a float = beats, or Duration.*).
lead.add("D5", 1).add("B4", 0.5).add("D5", 0.5).add("G5", 2)
lead.rest(2)

for n in ["G2", "D2", "E2", "C2"]:
    bass.add(n, Duration.WHOLE)
  • part.add(note_or_chord, duration) chains and returns the part. part.rest(duration) inserts silence.
  • Duration.WHOLE / HALF / QUARTER / EIGHTH / SIXTEENTH plus dotted variants (DOTTED_HALF, DOTTED_QUARTER, …), or pass a float in beats (1, 0.5, 0.25, 0.125).
  • Key(tonic, mode).progression("I", "V", "vi", "IV") returns Chords (lowercase numeral = minor, e.g. "i", "VI"). Key(...).chords lists the diatonic chords; Key(...).scale gives the scale tones. Chord.from_symbol("F#m7b5") parses any symbol.
  • Note names are scientific pitch (C4 = middle C). Tone.from_string("A1") builds an explicit pitch; tone.add(12)/tone.add(-12) shift octaves.

Read the full file on GitHub · 330 lines

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. 1mo ago First seen · 330 lines · 138 tokens per session scan A e916e8fa6057

Subscribe to this mod's changes

composing-with-pytheory is a skill published in the GitHub repository kennethreitz/pytheory-skill (3 stars, last pushed 4mo ago), licensed MIT. It adds 138 tokens to every session and 4,618 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to composing-with-pytheory, differing in 0 lines, and is treated as a copy.

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