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 skills add GuitarAlchemist/ga --skill common-tonesgit clone --depth 1 https://github.com/GuitarAlchemist/gaWrote 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/guitaralchemist/ga/common-tones)<a href="https://agentmods.dev/skills/guitaralchemist/ga/common-tones"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/common-tones/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.
<a href="https://agentmods.dev/skills/guitaralchemist/ga/common-tones"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/common-tones.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00091 | $0.01402 |
| Opus 5.5 | $0.00036 | $0.00561 |
| Sonnet 5.5 | $0.00018 | $0.00280 |
| Haiku 4.5 | $0.00009 | $0.00140 |
Grade A, and why
common-tones 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Common Tones Between Two Chords
When a user asks what notes two chords share, call ga_dsl_eval with closure name domain.commonTones. Don't compute the intersection mentally — the closure returns each shared note's interval role in BOTH chords (root / 3rd / 5th / 7th / 9th / 11th / 13th), and that role-mapping is exactly what the LLM gets wrong on extended/altered chords.
Why this skill uses ga_dsl_eval (not a keyhole tool)
This is the second canary for the DSL-eval pattern (PR #146 was the first, transpose). The domain.commonTones closure is already in GaClosureRegistry — exposed because its category is Domain. See docs/contracts/2026-05-06-ga-dsl-eval-contract.md (v0.1).
Calling the tool
Method: ga_dsl_eval
Args (flat key-value, all values as strings):
closureName="domain.commonTones"args.chord1— first chord symbol, e.g."Cmaj7","F#m7".args.chord2— second chord symbol.
Example invocation:
ga_dsl_eval(closureName: "domain.commonTones",
args: { "chord1": "Cmaj7", "chord2": "Am7" })
Returns a DslEvalResult. Read Result for the formatted shared-notes string (or ResultJson for the same value as a JSON-quoted string). On failure, read Error.Code and Error.Message.
Mapping user phrasings
- "What notes do Cmaj7 and Am7 share?" →
args = { "chord1": "Cmaj7", "chord2": "Am7" } - "Common tones between G and D7" →
args = { "chord1": "G", "chord2": "D7" } - "Pivot tones from F to Bb7" →
args = { "chord1": "F", "chord2": "Bb7" } - "What's shared between Cmaj9 and Em7?" →
args = { "chord1": "Cmaj9", "chord2": "Em7" }
Phrasing the answer
The closure returns a formatted string already. Surface it verbatim, then add a one-line interpretive hook tailored to the user's apparent intent (pivot, voice leading, modulation prep). Example:
Cmaj7 and Am7 share these notes:
- C → root of Cmaj7, minor third of Am7
- E → major third of Cmaj7, perfect fifth of Am7
- G → perfect fifth of Cmaj7, minor seventh of Am7
Three common tones — that's why Am7 is the canonical relative-vi substitute for C. Swap them anywhere in a progression with minimal harmonic disturbance.
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.
- 1mo ago First seen · 93 lines · 91 tokens per session scan A 69ad56e880e0
common-tones is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,402 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.