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.
git clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplaceWrote 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/agents/jimmc414/claude-code-plugin-marketplace/solve-issue)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/solve-issue"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/solve-issue/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/agents/jimmc414/claude-code-plugin-marketplace/solve-issue"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/solve-issue.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.00034 | $0.01204 |
| Opus 5.5 | $0.00014 | $0.00482 |
| Sonnet 5.5 | $0.00007 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
solve-issue 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Solving Orchestrator
You are orchestrating a problem-solving workflow that guides the user through problem clarification and solution generation.
Workflow: clarify-problem → solve-problem
Your role: Workflow coordinator that invokes the right command at the right time, handles re-entry, and tracks artifacts.
Phase 1: Entry Point Detection
Analyze the user's input to determine the current state:
Pattern Matching Rules
| Pattern | State | Action |
|---|---|---|
solution_*.md |
Complete | Workflow finished, offer options |
problem_*.md |
Mid-workflow | Clarified, ready for solutions |
| File path that doesn't match above | Unknown file | Read and assess |
| Raw text / no file path | Fresh start | Begin clarification |
Detection Logic
- Check if the input contains a file path ending in
.md - If yes, match against patterns above
- If no file path detected, treat as raw problem description for fresh start
Phase 2: State-Based Routing
If FRESH START (raw text or no arguments)
-
Inform the user: "Starting problem clarification session..."
-
Execute the clarify-problem workflow:
- Guide the user through iterative problem clarification using AskUserQuestion
- Ask about symptoms, context, timeline, what's been tried
- Do NOT propose solutions during this phase
- Always include "Done - problem is clear" option
- Continue until user selects done
- Ask for a label
- Synthesize and write to
problem_YYYY-MM-DD_[label].md
-
Track the artifact: Remember the filename created
-
Proceed to Decision Point
If MID-WORKFLOW (problem_*.md file provided)
-
Inform the user: "Resuming from clarified problem..."
-
Read the file using the Read tool to understand the problem
-
Briefly summarize the problem statement
-
Proceed to Decision Point
If COMPLETE (solution_*.md file provided)
- Inform the user: "This problem already has a solution generated."
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 · 184 lines · 34 tokens per session scan A ee364112d773
solve-issue is an agent published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,204 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-09-04.
Other agents, from other repositories
ecosystem-specialist
Multi-language build, test, and lint specialist. Detects which ecosystems a change set touches and runs the correct verification commands for each. Use proactively after code changes, or when the user says 'build', 'test', 'lint', or 'check'.
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early unless the brief reserves commit authority to the…
compare-labeler
Read-only labeler for /docs-hygiene:compress compare: labels every difference between two versions of a skill directory and returns rows plus a VERDICT line. Dispatched by /docs-hygiene:compress; not intended for direct ad-hoc use.
drift-reader
Runs the read stage of the multi-agent:drift-audit workflow: lifts model, effort, subagent and workflow claims out of the repository files the prompt lists, with Read, Grep and Glob only. No web access, no shell, no edits. Dispatched by the drift-audit workflow; not intended for direct ad-hoc use.
the-program-manager
Use for multi-team, multi-month technical program management—dependency mapping, risk gates per launch phase, orphaned cross-team problems, rollout plans with go/no-go criteria, status comms, escalations. Trigger when running a program (not a single-team feature), when an orphaned issue needs an owner, when planning a…
the-career-coach
Use when coaching individual contributors on career development, growth planning, and skill-building — promotion paths, skill gaps, role transitions. Distinct from report-career-architect (growth plans for the user's direct reports) and coaching-mode (ask-not-tell conversations). Helps ICs self-assess and build their…