Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install disciplineWrote 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/melodic-software/claude-code-plugins/pick-for-the-problem)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/pick-for-the-problem"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/pick-for-the-problem/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/melodic-software/claude-code-plugins/pick-for-the-problem"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/pick-for-the-problem.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.00119 | $0.01516 |
| Opus 5.5 | $0.00048 | $0.00606 |
| Sonnet 5.5 | $0.00024 | $0.00303 |
| Haiku 4.5 | $0.00012 | $0.00152 |
Grade A, and why
pick-for-the-problem 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pick for the problem
A drift corrector for selection discipline: the tool must fit the problem,
not the reflex. The shared method (re-anchor, audit the work in flight,
correct forward, report) lives in
${CLAUDE_PLUGIN_ROOT}/context/re-anchor-audit-correct.md.
Read it; this file adds only what is specific to selecting a tool, library,
framework, language, or approach.
The discipline this re-anchors
A selection is a design decision, not a reflex. Resolve the source of truth
per the method doc's ladder: if the consuming project states a
technology-selection or dependency-adoption rule in its own CLAUDE.md /
.claude/rules/, re-anchor THAT. Otherwise re-anchor this portable
baseline.
The five selection sins, an unexamined choice usually traces to one:
- Habit. "I always use X." The reach is muscle memory, not analysis.
- Availability. "X is already at hand." Convenience picked it, not fit.
- Incumbency. "the repo already uses X, so new work assumes X." Current state is treated as the requirement.
- Preconception. "I came in believing X is the answer." The verdict preceded the problem.
- Popularity. "Everyone uses X; the top template ships it." Adoption stood in for correctness, unchecked against the principle X claims to serve.
The discipline that replaces them:
- Define the actual problem first. Name what is being solved, the real requirements, before any candidate is on the table.
- Survey the field. More than one candidate, judged against the stated requirements and the plausible future ones (variables that could shift and turn a choice into future pain).
- Walk the preference ladder, an earlier rung wins when it covers the
requirements and the plausible future requirements:
- Native. What the platform, language, or framework already provides: no new dependency, no new coupling.
- Official / authoritative, the first-party or canonical option when native falls short.
- Vetted third-party. Only when the rungs above genuinely miss, and only if it is well-maintained, well-known, safe, and secure.
- Every dependency is a coupling point. Weigh, at adoption time, the cost this coupling can impose later: abandonment, a pricing pivot, a license change, security posture, and exit cost.
- Building what already exists is a finding. Re-implementing a solved, well-served problem (native or vetted) is a selection error in the other direction. Name it.
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.
- 5d ago Changed · -10 lines · +1 tokens per session e3c04f76d80b
- 8d ago Changed 7c8693fb4591
- 15d ago Changed · +2 lines a1eca09d55ba
- 21d ago Changed · +6 lines 1f7b492fb9c2
- 22d ago Changed · -20 tokens per session 8ccfb2218d9c
- 27d ago Changed e3a0cd3fb9f4
- 1mo ago Changed · -3 lines 626acd7aeaf3
- 1mo ago First seen · 125 lines · 138 tokens per session scan A 1b2890cef832
pick-for-the-problem is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 1,516 once invoked, about $0.0005 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
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
return-none-for-failure
For graceful failure: return None or False instead of exceptions, let caller decide how to handle failure.