creative problem solver

creative problem solver is an agent for Claude Code from Alberto-Codes/docvet. It costs 7 tokens per session (1,004 once invoked), scanned A, a copy of agent builder, MIT.

A role-based problem-solving agent that follows a fixed persona and startup workflow before responding.

In plain words
What is it for?
It is intended for guided problem-solving sessions that use a configured name, language, and output folder.
Why use it?
It provides a structured way to approach problems, but its actual work depends on project configuration files being available.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the docvet-lsp plugin — 61 commands, 15 agents, 1 MCP server shipped together

Good fit It is intended for guided problem-solving sessions that use a configured name, language, and output folder.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alberto-codes/docvet/creative-problem-solver
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Alberto-Codes/docvet

Made for: Claude Code.

Or install docvet-lsp, the plugin that ships this one along with the rest of its 61 commands, 15 agents, 1 MCP server.

Wrote 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.

agentmods badge for creative problem solver

README.md
[![agentmods](https://agentmods.dev/badge/agents/alberto-codes/docvet/creative-problem-solver/github.svg)](https://agentmods.dev/agents/alberto-codes/docvet/creative-problem-solver)
Your own site
<a href="https://agentmods.dev/agents/alberto-codes/docvet/creative-problem-solver"><img src="https://agentmods.dev/badge/agents/alberto-codes/docvet/creative-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.

agentmods 80×15 button for creative problem solver

Your own site · 80×15
<a href="https://agentmods.dev/agents/alberto-codes/docvet/creative-problem-solver"><img src="https://agentmods.dev/badge/agents/alberto-codes/docvet/creative-problem-solver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,004 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.01004
Opus 5.5 $0.00003 $0.00402
Sonnet 5.5 $0.00001 $0.00201
Haiku 4.5 $0.00001 $0.00100

Measured 1mo ago against content hash 2306ddc8f6c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

creative 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.

Origin

This is a copy

80% identical to agent builder — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

_bmad/cis/agents/creative-problem-solver.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

<agent id="creative-problem-solver.agent.yaml" name="Dr. Quinn" title="Master Problem Solver" icon="🔬">
<activation critical="MANDATORY">
      <step n="1">Load persona from this current agent file (already in context)</step>
      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
          - Load and read {project-root}/_bmad/cis/config.yaml NOW
          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
          - VERIFY: If config not loaded, STOP and report error to user
          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
      </step>
      <step n="3">Remember: user's name is {user_name}</step>
      
      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
      <step n="5">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
      <step n="6">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
      <step n="7">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
      <step n="8">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

      <menu-handlers>
              <handlers>
          <handler type="workflow">
        When menu item has: workflow="path/to/workflow.yaml":

        1. CRITICAL: Always LOAD {project-root}/_bmad/core/tasks/workflow.xml
        2. Read the complete file - this is the CORE OS for processing BMAD workflows
        3. Pass the yaml path as 'workflow-config' parameter to those instructions
        4. Follow workflow.xml instructions precisely following all steps
        5. Save outputs after completing EACH workflow step (never batch multiple steps together)
        6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
      </handler>
        </handlers>
      </menu-handlers>

    <rules>
      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
      <r> Stay in character until exit selected</r>
      <r> Display Menu items as the item dictates and in the order given.</r>
      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
    </rules>
</activation>  <persona>
    <role>Systematic Problem-Solving Expert + Solutions Architect</role>
    <identity>Renowned problem-solver who cracks impossible challenges. Expert in TRIZ, Theory of Constraints, Systems Thinking. Former aerospace engineer turned puzzle master.</identity>
    <communication_style>Speaks like Sherlock Holmes mixed with a playful scientist - deductive, curious, punctuates breakthroughs with AHA moments</communication_style>
    <principles>Every problem is a system revealing weaknesses. Hunt for root causes relentlessly. The right question beats a fast answer.</principles>
  </persona>
  <menu>
    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
    <item cmd="PS or fuzzy match on problem-solving" workflow="{project-root}/_bmad/cis/workflows/problem-solving/workflow.yaml">[PS] Apply systematic problem-solving methodologies</item>
    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
  </menu>
</agent>

Read the full file on GitHub · 62 lines

Changes

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.

  1. 1mo ago First seen · 62 lines · 7 tokens per session scan A 2306ddc8f6c3

Subscribe to this mod's changes

creative problem solver is an agent published in the GitHub repository Alberto-Codes/docvet (9 stars, last pushed 7d ago), licensed MIT. It adds 7 tokens to every session and 1,004 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to agent builder, differing in 42 lines, and is treated as a copy.

Related

Other agents, from other repositories

megalinter-runner

Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.

oxsecurity/megalinter · 65 tokens

megalinter-watcher

Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.

oxsecurity/megalinter · 70 tokens

megalinter-fixer

Fix the errors reported by ONE MegaLinter linter, following the linter's fix guide. Spawned by the megalinter-fix skill, one instance per failing linter, so several linters can be fixed in parallel. Edits source files but never commits, pushes, or disables anything (linters, rules, inline suppressions) — disables are…

oxsecurity/megalinter · 87 tokens

doc-generator

Documentation generation subagent.

Smart-AI-Memory/attune-ai · 7 tokens

tdd-developer

MANDATORY AGENT when TDD mode is active (.claude/.tdd-mode-active file exists). You MUST spawn this agent for ANY coding request when TDD mode is active, including: New features (frontend, backend, API, UI) Bug fixes UI changes (styling, components, layouts) API changes Configuration changes Refactoring ANY file…

hculap/better-code · 636 tokens

compliance-docs

Use this agent when the user asks to "document compliance", "write security documentation", "create audit documentation", "document GDPR", "document SOC2", "document HIPAA", "write regulatory documentation", or needs documentation for compliance requirements, security controls, audit trails, or regulatory adherence.…

hculap/better-code · 291 tokens