playing-guitar-with-pytheory

playing-guitar-with-pytheory is a skill for Claude Code from kennethreitz/pytheory-skill. It costs 165 tokens per session (2,429 once invoked), scanned A, a copy of playing-guitar-with-pytheory, MIT.

A Python tool for working with guitar and other string-instrument fingerboards. It represents chord shapes, notes, scales, tunings, and capo positions, and can display them as tabs or diagrams.

In plain words
What is it for?
Finding chord fingerings, printing ASCII tablature, identifying chords, drawing scale diagrams, handling alternate tunings and capos, creating Nashville number charts, and tuning through a microphone.
Why use it?
It turns music-theory questions into concrete finger placements and readable playing instructions instead of requiring manual fretboard calculations.

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 Finding chord fingerings, printing ASCII tablature, identifying chords, drawing scale diagrams, handling alternate tunings and capos, creating Nashville number charts, and tuning through a microphone.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kennethreitz/pytheory-skill/playing-guitar-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 playing-guitar-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 playing-guitar-with-pytheory

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kennethreitz/pytheory-skill/playing-guitar-with-pytheory"><img src="https://agentmods.dev/badge/skills/kennethreitz/pytheory-skill/playing-guitar-with-pytheory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 165 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,429 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.00165 $0.02429
Opus 5.5 $0.00066 $0.00972
Sonnet 5.5 $0.00033 $0.00486
Haiku 4.5 $0.00016 $0.00243

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

Security

Grade A, and why

playing-guitar-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 playing-guitar-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/playing-guitar-with-pytheory/SKILL.md · 213 lines

How it starts

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

Playing guitar (and strings) with PyTheory

PyTheory models the fretboard: chord shapes, fingerings, tablature, scale diagrams, alternate tunings, and chord identification — for guitar and ~20 other stringed instruments — plus a real-time tuner. The fretboard tools are pure Python (run a script or one-liner); the tuner is a CLI that listens to your mic.

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.

Fingerings, chord shapes & tab

from pytheory import Fretboard, Chord

fb = Fretboard.guitar()

print(fb.tab("Am"))          # ASCII tablature for a chord (high e on top)
# A minor
# e|--0--
# B|--1--
# G|--2--
# D|--2--
# A|--0--
# E|--x--

shape = fb.chord("Am")       # a Fingering object
shape.positions              # (None, 0, 2, 2, 1, 0)  — None = muted string
shape.string_names           # ('E', 'A', 'D', 'G', 'B', 'e')  — data model, low-to-high
print(shape.tab())           # same ASCII tab (always high-to-low display)
  • Fretboard.guitar() and friends build a fretboard; .chord("Cmaj7") returns a Fingering, .tab("Cmaj7") returns the ASCII tab string directly.
  • .fingering(0, 2, 2, 1, 0, 0) builds a Fingering from explicit fret numbers (low-to-high), e.g. to check a shape you have in mind.
  • A Fingering has .positions, .string_names, .tones, .tab(), .identify(), and .to_chord().

Charted-chord coverage: .chord()/.tab() look the name up in a library of ~144 common voicings — every root in major, minor, 5, 6, 7, m7, maj7, 9, m9, maj9, and dim. Names outside that set (e.g. sus4, m7b5, aug, add9) raise KeyError. For those, either build the shape yourself with .fingering(...), or work from the chord's notes via Chord.from_symbol("F#m7b5") (see "Identify a chord"). CHARTS["western"].keys() lists everything charted.

Other instruments

All take the same .chord() / .tab() / .scale_diagram() API:

Read the full file on GitHub · 213 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 · 213 lines · 165 tokens per session scan A 6202d2eec193

Subscribe to this mod's changes

playing-guitar-with-pytheory is a skill published in the GitHub repository kennethreitz/pytheory-skill (3 stars, last pushed 4mo ago), licensed MIT. It adds 165 tokens to every session and 2,429 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to playing-guitar-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