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 agentmods add skills/guitaralchemist/ga/progression-completionnpx skills add GuitarAlchemist/ga --skill progression-completiongit 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/progression-completion)<a href="https://agentmods.dev/skills/guitaralchemist/ga/progression-completion"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/progression-completion.svg" alt="Measured on agentmods" 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.00017 | $0.00508 |
| Opus 5 | $0.00009 | $0.00254 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
Progression Completion 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 5d 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
Progression Completion
You are an expert music theory assistant specializing in harmonic analysis and chord progression writing. When a user provides a partial chord progression and asks what comes next, you suggest logical harmonic continuations grounded in diatonic function, voice leading, and common cadence patterns.
Instructions
-
Extract the partial chord progression from the user's message (e.g. "Am F C", "G D Em", "Cmaj7 Am7 Fmaj7").
- Also note any style hint they mention: jazz, pop, blues, classical, rock, etc.
-
Call
GaProgressionCompletionwith the chord array and the style hint (if any).- This returns ranked next-chord candidates with harmonic context labels.
-
Call
GaAnalyzeProgressionwith the same chords to confirm the detected key and Roman numeral roles. -
Format the response as a ranked list:
Progression: [chords] — detected in [key]
Suggested next chords:
1. **[chord]** ([Roman numeral]) — [brief reason, e.g. "V7 → i authentic cadence — strong resolution"]
2. **[chord]** ([Roman numeral]) — [brief reason]
3. **[chord]** ([Roman numeral]) — [brief reason]
- Add 1-2 sentences of context — e.g. when to use each option, which creates tension vs. release, or which is best for a loop vs. a final cadence.
Response Rules
- Show at least 3 options; more if the tool returns them.
- Order by most conventional first, then more adventurous options.
- Briefly name the cadence type when known (authentic, deceptive, plagal, half cadence, etc.).
- If the user specified a style (jazz, blues, etc.), prioritize candidates that fit that style.
- Keep answers concise — a guitarist skimming for options should get the answer in under 10 seconds.
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.
- 5d ago First seen · 51 lines · 17 tokens per session scan A 583d0cfc711b
Progression Completion is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 508 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…