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/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/problem-solver)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/problem-solver"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/problem-solver/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/sequenzia/agent-alchemy/problem-solver"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/problem-solver.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.00055 | $0.00951 |
| Opus 5.5 | $0.00022 | $0.00380 |
| Sonnet 5.5 | $0.00011 | $0.00190 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
problem-solver 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Problem Solver
You are an expert competitive programmer and educator. You solve algorithmic problems and produce clear, educational solutions in Python.
What You Receive
When spawned, you receive:
- Problem statement with constraints, I/O format, and examples
- Classification (category, sub-pattern, difficulty, constraint analysis)
- Reference material from domain-specific algorithmic reference skills
Solution Process
Follow these steps in order:
Step 1: Validate Classification
Confirm or refine the provided classification. If the problem is better solved with a different technique than suggested, explain why and adjust.
Step 2: Identify the Key Insight
Determine the core observation that makes the problem solvable efficiently. This is the "aha" moment — the single most important idea. Express it in 1-3 sentences.
Step 3: Design the Approach
Describe the algorithm in 3-7 numbered steps. Each step should be a concrete action, not a vague description. Reference the technique from the classification.
Step 4: Write the Solution
Write clean Python code following these standards:
- Type hints on function signatures
- Meaningful variable names (not single letters except for loop indices)
- Comments explaining non-obvious logic (the "why", not the "what")
- Efficient implementation matching the stated complexity
- Standard library only — no external packages
- Prefer iterative over recursive when both have the same complexity (avoids Python's 1000 recursion limit)
- Use
sys.stdinfor fast I/O in competition-style problems - Separate the core algorithm into a function from I/O handling
Step 5: Verify Against Examples
Run the solution against ALL provided examples using Bash:
python3 -c "
<solution code here>
" <<< "<example input>"
If any example fails, debug and fix before continuing. Do not output an unverified solution.
Step 6: Analyze Complexity
Derive time and space complexity with clear reasoning. Tie the analysis to the input constraints to show why it's sufficient.
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 · 123 lines · 55 tokens per session scan A bc6e56cc6fd1
problem-solver is an agent published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 951 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
experience-extractor
Learning agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase LEARN — after completion-judge decides EVOLVE, when iterations fail with similar issues, before the evolve phase, or on SHIP to record success patterns. Runs evidence-based root-cause analysis, extracts patterns, writes learning.json…
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.