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/marinahaugen/polymorph-mindset-plugins/commit-dancenpx skills add marinahaugen/polymorph-mindset-plugins --skill commit-dancegit clone --depth 1 https://github.com/marinahaugen/polymorph-mindset-pluginsWhat 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 | $0.00052 | $0.03051 |
| Opus 5 | $0.00026 | $0.01525 |
| Sonnet 5 | $0.00010 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
commit-dance 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 yesterday.
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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Dance
Overview
Re-cluster the commits on a feature branch into a clean pedagogical narrative after the original work has accumulated additional fixes, bug repairs, or review tweaks. The "dance" is the choreographed sequence:
backup → soft reset → re-commit pedagogically → verify zero-diff → force-push with lease
Core invariant: the final tree must be byte-for-byte identical to the pre-dance tree. Only the commit history changes shape — never the working tree.
When to Use
- Long PR review: many "address review" / "fix typo" / "wip" commits accumulated; reviewer wants to walk the changes as a story
- Combining the original feature work + bug fixes discovered during testing into thematic chapters
- A branch that has the right code but a history that hides the architecture
- BEFORE merging a PR you want to be readable later as a learning artifact (
pedagogical-pr-review)
Don't use when:
- The branch has merged commits from main/development (rebase those out first, separately)
- Other people are actively pulling the branch (force-push will require them to reset)
- The history is already clean and the only goal is "tidy commit messages" (use
git commit --amendper commit instead) - You're not certain about the chapter boundaries (do
pedagogical-pr-reviewor planning first)
Quick Reference
| Step | Command | Critical |
|---|---|---|
| 1. Verify branch | git branch --show-current && git status --porcelain |
Tree clean OR only intended unstaged fixes |
| 2. Backup tag | git tag <branch>-original-$(date +%Y-%m-%d-%H%M) |
Before anything destructive |
| 3. Backup commit log | git log --oneline <base>..HEAD > /tmp/<branch>-original.txt |
For human reference |
| 4. (optional) Backup branch | git push origin <branch>:<branch>-backup |
Offer; never auto |
| 5. Plan chapters | Show original commits + file diff; propose mapping | Get user approval |
| 6. Soft reset | git reset --mixed $(git merge-base HEAD <base>) |
--mixed, NEVER --hard |
| 7. Per chapter | git add <files> && git commit -m "..." |
Stage subsets, not -A |
| 8. Verify zero-diff | git diff HEAD <backup-tag> shows ONLY intentional fixes |
Stop if anything unexpected |
| 9. Run tests | Project-specific (lint + unit + integration) | Confirm new HEAD is functional |
| 10. Push | git push --force-with-lease |
NEVER --force |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 254 lines · 52 tokens per session scan A b827d8228537
commit-dance is a skill published in the GitHub repository marinahaugen/polymorph-mindset-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 3,051 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…