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.
npx agentmods add commands/lesleslie/graphics-mcp/graphics-convertgit clone --depth 1 https://github.com/lesleslie/graphics-mcpWrote 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/commands/lesleslie/graphics-mcp/graphics-convert)<a href="https://agentmods.dev/commands/lesleslie/graphics-mcp/graphics-convert"><img src="https://agentmods.dev/badge/commands/lesleslie/graphics-mcp/graphics-convert.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00403 |
| Opus 5 | $0.00011 | $0.00201 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
graphics-convert 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 5d 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
/graphics-convert
Convert an image to a different format using the graphics MCP server.
Usage
/graphics-convert <image-path> <target-format> [--quality N] [--optimize]
Arguments:
<image-path>: absolute path to the source image file. Must be under one of the directories returned bymcp__graphics__list_allowed_directories.<target-format>: one of the formats returned bymcp__graphics__list_supported_formats(typicallyjpeg,png,gif,bmp,webp,tiff).--quality N: optional, integer 1-100. Used for lossy targets (JPEG/WEBP).--optimize: optional flag. Enables format-specific size optimization.
Workflow
- Call
mcp__graphics__list_allowed_directoriesto confirm<image-path>is under a permitted root. - Call
mcp__graphics__list_supported_formatsto validate the requested<target-format>. - Call
mcp__graphics__get_image_infowith<image-path>to capture source dimensions and metadata for the report. - Call
mcp__graphics__convert_imagewithimage_path,output_format, and any optional flags. - Report the output path and the size delta (source bytes vs. converted bytes).
Example
/graphics-convert /Users/les/Pictures/photo.png webp --quality 85 --optimize
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.
- 5d ago First seen · 33 lines · 22 tokens per session scan A 783cc3f295d6
graphics-convert is a command published in the GitHub repository lesleslie/graphics-mcp (1 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 22 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.