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/Borda/vision-deliveryWrote 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/borda/vision-delivery/cv-problem-solver)<a href="https://agentmods.dev/agents/borda/vision-delivery/cv-problem-solver"><img src="https://agentmods.dev/badge/agents/borda/vision-delivery/cv-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/borda/vision-delivery/cv-problem-solver"><img src="https://agentmods.dev/badge/agents/borda/vision-delivery/cv-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.00174 | $0.00348 |
| Opus 5.5 | $0.00070 | $0.00139 |
| Sonnet 5.5 | $0.00035 | $0.00070 |
| Haiku 4.5 | $0.00017 | $0.00035 |
Grade A, and why
cv-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.
What it actually says
This is the Claude Code adapter for the vision-delivery problem-solver entry point.
The canonical Claude recipe lives in claude-skills/solve-cv-task/SKILL.md. Read that file completely before taking action, then follow it as the active workflow.
Keep this adapter thin:
- Preserve Claude-specific frontmatter here:
tools,model,color, and trigger text. - Do not add routing tables, workflow steps, safety gates, or composition protocols here.
- When behavior changes, edit
claude-skills/solve-cv-task/SKILL.mdand keep this adapter's trigger/skip description aligned with the canonical skill.
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 · 22 lines · 174 tokens per session scan A 69720fd534df
cv-problem-solver is an agent published in the GitHub repository Borda/vision-delivery (4 stars, last pushed 13d ago), licensed Apache-2.0. It adds 174 tokens to every session and 348 once invoked, about $0.0007 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-31.
Other agents, from other repositories
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
turbo-brain
Use only when superb:turbo-pipeline dispatches its two brains to settle one engineering question the user is no longer available to answer. One of two independent readers given the identical question and context; returns one JSON object with an answer and an integer confidence 0-100, nothing else. Never dispatched by…
architecture-discovery
Use when a product idea needs its technical decisions surfaced as questions before any of them are made — invoked by superb:craft once per session, after the idea is stated and before the first question round, for software projects whose stack is not yet decided. Returns candidate questions only; never chooses a stack…
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.
pipeline-auto-intent-reader
Use only at superb:pipeline-auto stage 01, to read what the user actually asked for and return it as a strict JSON hypothesis. One of three independent readers. Reads and reports; never designs, never proposes, never chooses a stack.
data-engineer
Builds data pipelines for ETL/ELT, manages analytics storage (data warehouse/lake), and ensures data quality. Optimizes data ingestion, transformation, and reporting. Use when the user asks to build data pipelines, design analytics infrastructure, or improve data quality.