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 marinahaugen/polymorph-mindset-plugins --skill pedagogical-pr-reviewgit clone --depth 1 https://github.com/marinahaugen/polymorph-mindset-pluginsWrote 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/marinahaugen/polymorph-mindset-plugins/pedagogical-pr-review)<a href="https://agentmods.dev/skills/marinahaugen/polymorph-mindset-plugins/pedagogical-pr-review"><img src="https://agentmods.dev/badge/skills/marinahaugen/polymorph-mindset-plugins/pedagogical-pr-review/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/marinahaugen/polymorph-mindset-plugins/pedagogical-pr-review"><img src="https://agentmods.dev/badge/skills/marinahaugen/polymorph-mindset-plugins/pedagogical-pr-review.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.00109 | $0.01575 |
| Opus 5 | $0.00055 | $0.00788 |
| Sonnet 5 | $0.00022 | $0.00315 |
| Haiku 4.5 | $0.00011 | $0.00158 |
Grade A, and why
pedagogical-pr-review 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 9d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pedagogical PR Review
A structured file-by-file walkthrough of a pull request that prioritizes understanding over speed. The reviewer explains why changes make sense, highlights design patterns, and checks comprehension before proceeding.
This is different from a standard code review. A standard review finds bugs and style issues. This review teaches the reader what the PR does, why the approach was chosen, and what patterns they should take away.
Process
Phase 1: Orientation
Before touching individual files, build the big picture:
- Fetch the PR — get title, description, file list, and full diff
- Explain the problem — what bug or feature motivated this PR? Use diagrams (ASCII flow diagrams, tables, before/after comparisons) to make the problem visceral
- Explain the solution — at a high level, what approach was chosen? Why this approach over alternatives? Show the before/after architecture
- Ask the user which file categories to skip — common skippable categories:
- Auto-generated files (codegen, lockfiles)
- Translation/locale files
- Config files with trivial changes
- Test snapshots
Phase 2: File Planning
Build the file list and present it as a numbered checklist with status markers:
Progress: [0/12]
1. src/hooks/useFoo.ts (NEW)
2. src/hooks/useBar.ts (DELETED)
3. src/components/Widget.tsx
...
Ordering matters. Don't go alphabetically. Order files so that understanding builds:
- Deleted files first (or paired with their replacement) — understanding what was removed and why helps the reader grasp what the new code replaces
- New shared utilities/helpers — these are referenced by other files, so explain them before their consumers
- Core logic files — the heart of the change
- Consumer files — components/pages that use the new logic
- Tests last — they validate everything above, so they make more sense after seeing the implementation
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.
- 9d ago First seen · 154 lines · 109 tokens per session scan A 46f8e13bc6dd
pedagogical-pr-review is a skill published in the GitHub repository marinahaugen/polymorph-mindset-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 1,575 once invoked, about $0.0005 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
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
vertical-hr-recruiting
Domain-knowledge primer for the HR & recruiting vertical (ATS, onboarding, workforce scheduling, engagement). Applied by architect/pm during spec authoring so they aren't naive about hiring pipelines, the admitted offer→onboard data-carry gap, EEO/I-9 compliance, and shift-coverage rules. Stops the four products from…
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
vertical-retail
Retail & e-commerce domain knowledge for SMB storefront products (storefront, inventory, pricing, cart-recovery). Codifies the vocabulary (SKU vs variant, reorder point, COGS/margin, ATS, AOV), the non-obvious rules (Shopify owns the storefront — don't fight it head-on; the wedge is multichannel inventory + reorder…
vertical-fitness
Domain-knowledge pack for fitness & wellness (boutique studios, gyms, coaches, on-demand brands) — the membership vocabulary, non-obvious billing/booking rules, and retention realities a builder must know so fitness products aren't speced naive. Covers the four products this niche ships (class-booking, coaching…