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 scale-infogit 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/scale-info)<a href="https://agentmods.dev/skills/guitaralchemist/ga/scale-info"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/scale-info/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/scale-info"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/scale-info.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.00041 | $0.01100 |
| Opus 5.5 | $0.00016 | $0.00440 |
| Sonnet 5.5 | $0.00008 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
scale-info 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notes of a Major or Minor Key
When a user asks for the notes of a key (or scale), call the ga_scale_get_notes MCP tool. Do NOT recall the notes from training knowledge — different sources spell the same key differently (D# minor vs Eb minor) and the LLM will confidently produce wrong notes for less-common keys.
Calling the tool
The tool takes two arguments:
root— string, e.g."C","F#","Bb". Case-insensitive.mode—"major"or"minor"(also accepts"maj"/"min").
It returns a structured result:
Notes— string array of seven note names in ascending order.KeySignature— human-readable, e.g."2 sharps"or"no sharps or flats".RelativeKey— name of the relative major or minor.Error— non-null only when the input could not be parsed.
Mapping user phrasings to arguments
- "What notes are in C major?" →
root="C",mode="major". - "Show me the F# minor scale" →
root="F#",mode="minor". - "List the notes in Bb major" →
root="Bb",mode="major". - "What is D minor?" / "Tell me about D minor" → treat as a notes request:
root="D",mode="minor". - "What's in the key of E?" — the user did not specify mode. Ask first rather than guessing: "E major or E minor?"
Phrasing the answer
Use the Notes array verbatim, joined with – (en-dash) or commas. Add the KeySignature and RelativeKey as a separate sentence. Example:
The C major scale has 7 notes: C – D – E – F – G – A – B. Key signature: no sharps or flats. Relative minor: A minor.
If Error is non-null, surface the message verbatim and ask the user to clarify.
When to ask for clarification
- User names a chord rather than a key: "what notes are in a C major chord" → that's a chord-intervals question; defer to the
chord-infoskill. Do NOT callga_scale_get_notes. - User asks about modes (Dorian, Phrygian, etc.) other than major / minor — defer to the
modesskill, which lists the seven major-scale modes with their degree formulas.ga_scale_get_notesitself only returns major or minor. - User asks for a scale other than the diatonic 7-note one (whole-tone, blues, pentatonic, harmonic minor): decline rather than fabricating notes.
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 · 86 lines · 41 tokens per session scan A d7958fe02e84
scale-info is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,100 once invoked, about $0.0002 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.