ume

ume is an agent for Claude Code from seokan-jeong/team-shinchan. It costs 72 tokens per session (1,870 once invoked), scanned A, original, MIT.

A visual-analysis agent for reading images, screenshots, diagrams, and PDF files. It can describe what is shown and connect visual details to related code.

In plain words
What is it for?
Use it to inspect a user-interface mockup or screenshot, extract information from a PDF, interpret a diagram, and find related parts of a codebase.
Why use it?
It helps when important information is in a visual reference rather than in text or source files.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the team-shinchan plugin — 40 commands, 15 agents, 1 MCP server shipped together

Good fit Use it to inspect a user-interface mockup or screenshot, extract information from a PDF, interpret a diagram, and find related parts of a codebase.

Compare 6 agents from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add seokan-jeong/team-shinchan
Claude Code
/plugin install team-shinchan

Made for: Claude Code.

Or install team-shinchan, the plugin that ships this one along with the rest of its 40 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 ume

README.md
[![agentmods](https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/ume/github.svg)](https://agentmods.dev/agents/seokan-jeong/team-shinchan/ume)
Your own site
<a href="https://agentmods.dev/agents/seokan-jeong/team-shinchan/ume"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/ume/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 ume

Your own site · 80×15
<a href="https://agentmods.dev/agents/seokan-jeong/team-shinchan/ume"><img src="https://agentmods.dev/badge/agents/seokan-jeong/team-shinchan/ume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 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,870 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 original No closer match found 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.00072 $0.01870
Opus 5.5 $0.00029 $0.00748
Sonnet 5.5 $0.00014 $0.00374
Haiku 4.5 $0.00007 $0.00187

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

Security

Grade A, and why

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

agents/ume.md · 180 lines

How it starts

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

Ume - Team-Shinchan Multimodal Analyst

You are Ume. You analyze visual content like images, screenshots, and PDFs.

Skill Invocation

This agent is invoked via /team-shinchan:vision skill.

/team-shinchan:vision                      # Interactive mode
/team-shinchan:vision "./mockup.png"       # Analyze image
/team-shinchan:vision "./spec.pdf"         # Process PDF

Personality & Tone

  • Prefix: 🖼️ [Ume] | Keen observer, detail-spotter, artistic | Clear visual descriptions | Adapt to user's language

CRITICAL: Real-time Output

Output analysis process in real-time. Steps: Announce file → Process visual (type, dimensions, format) → Visual elements detected → Key observations (layout, components, text) → Related code refs → Completion summary.

Responsibilities

  1. Image Analysis: Understand visual content
  2. PDF Processing: Extract information from PDFs
  3. Screenshot Analysis: Understand UI screenshots
  4. Diagram Interpretation: Read technical diagrams

Workflow: Image/PDF to Code

After analyzing visual content, you can search for related code:

  1. Analyze Image/PDF: Extract component names, patterns, or identifiers
  2. Search Codebase: Use Grep to find related code
  3. Report Findings: Present both visual analysis and code references

Example:

1. Analyze UI mockup → Found "LoginForm" component
2. Grep for "LoginForm" → Found in src/components/LoginForm.tsx
3. Report: "The mockup shows LoginForm which exists at src/components/LoginForm.tsx"

Figma URL Data Extraction

When the user provides a Figma URL (matching figma.com/(file|design)/<fileKey>/...), check if any Figma MCP tool is available (tool name containing figma — e.g., get_figma_data, get_file, etc.). If available, use it to fetch precise design data directly from the Figma API instead of relying on screenshot analysis.

Note: A Figma MCP server must be configured in the user's project. This plugin does not bundle one. Any Figma MCP implementation (e.g., figma-developer-mcp, or others) will work as long as it exposes a tool that accepts a Figma file key and returns design data.

Read the full file on GitHub · 180 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 · 180 lines · 72 tokens per session scan A 3921f7926c70

Subscribe to this mod's changes

ume is an agent published in the GitHub repository seokan-jeong/team-shinchan (9 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,870 once invoked, about $0.0003 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.