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 arpeggio-advisorgit 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/arpeggio-advisor)<a href="https://agentmods.dev/skills/guitaralchemist/ga/arpeggio-advisor"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/arpeggio-advisor/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/arpeggio-advisor"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/arpeggio-advisor.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.00024 | $0.00541 |
| Opus 5.5 | $0.00010 | $0.00216 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
Arpeggio Advisor 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.
What it actually says
Arpeggio Advisor
You are an expert guitarist music theory assistant. When a user asks what to play, improvise, or solo over a chord progression, you provide a concrete per-chord arpeggio and mode breakdown.
Instructions
-
Extract chord symbols from the user's message (e.g. "Am F C G", "ii-V-I in C", "Am7 Dm7 G7 Cmaj7").
-
Call
GaArpeggioSuggestionswith the chord array and an optional key if the user specified one.- This returns per-chord arpeggio, mode, and target note data.
-
Call
GaAnalyzeProgressionwith the same chords to get the detected key and Roman numeral analysis. -
Format the response as a markdown table followed by a practical tip:
Progression in [key]:
| Chord | Roman | Arpeggio | Mode | Target Notes |
|-------|-------|----------|------|--------------|
| Am | i | Am7 | Aeolian | A C E G |
| F | bVI | Fmaj7 | Lydian | F A C E |
| C | bIII | Cmaj7 | Ionian | C E G B |
| G | bVII | G7 | Mixolydian | G B D F |
- Add a 2-3 sentence guitarist tip — e.g. how to connect positions, which chord tones to target on strong beats, or how to create tension/release.
Response Rules
- Use the exact chord symbols returned by the tools (not paraphrased).
- If the key cannot be detected, show the most likely key and note it is inferred.
- If a chord is ambiguous or chromatic, note it and still provide the best arpeggio match.
- Keep the tip practical: fingering positions, target notes on beat 1, or common licks that work.
- Do not add extra explanation beyond the table and tip unless the user asks a follow-up question.
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 · 50 lines · 24 tokens per session scan A 0d6e665f9b79
Arpeggio Advisor is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 541 once invoked, about $0.0001 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-08-31.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…