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 skills/cmdr-chara/codex-toolkit/screenshot-to-interfacenpx skills add cmdr-chara/codex-toolkit --skill screenshot-to-interfacegit clone --depth 1 https://github.com/cmdr-chara/codex-toolkitWrote 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/skills/cmdr-chara/codex-toolkit/screenshot-to-interface)<a href="https://agentmods.dev/skills/cmdr-chara/codex-toolkit/screenshot-to-interface"><img src="https://agentmods.dev/badge/skills/cmdr-chara/codex-toolkit/screenshot-to-interface.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.00072 | $0.01797 |
| Opus 5 | $0.00036 | $0.00898 |
| Sonnet 5 | $0.00014 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
screenshot-to-interface 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Screenshot to Interface
Treat references as evidence, not as a bitmap to trace blindly. Reconstruct the underlying layout and behavior while preserving maintainability and rights.
Trigger boundary
Use this skill for:
- implementing a page, screen, component, or flow from screenshots;
- translating a design comp into responsive components;
- auditing why an implementation differs from its reference;
- inferring a coherent component/system model from multiple visual states.
Do not trigger for:
- deciding an original visual direction without a reference—use
product-design-director; - a production web/mobile audit unrelated to reference fidelity—use the platform builder;
- extracting or redistributing protected assets without permission;
- image OCR or screenshot transcription where no interface reconstruction is requested.
Required inputs
Obtain or record as unknown:
- all reference images and their source/provenance;
- pixel dimensions, device scale factor, viewport, orientation, theme, locale, and state if known;
- target repository, stack, routes, and existing design system;
- required interactions, responsive range, browsers/devices, and accessibility target;
- asset rights and available original logos/icons/fonts/images;
- acceptable fidelity tolerance and whether content may be adapted.
Do not infer one desktop screenshot as the complete responsive specification.
Provenance
This skill is an original restructuring that selectively adapts visual-reference and fidelity concepts from Leonxlnx/taste-skill. Read references/provenance.md and preserve the root notice.
Safety baseline
- Inspect repository and working-tree state before editing.
- Reuse existing tokens/components when they can express the reference without distortion.
- Do not replace project architecture, framework, or styling system solely for visual convenience.
- Do not embed screenshots as the interface, hard-code coordinates for one viewport, or use inaccessible canvas/text images for ordinary UI.
- Do not download fonts/assets from a reference without rights and license evidence.
- Preserve user code and keep generated or broad formatting changes out of the diff.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 205 lines · 72 tokens per session scan A e8e6db40ecd6
screenshot-to-interface is a skill published in the GitHub repository cmdr-chara/codex-toolkit (2 stars, last pushed 7d ago), licensed MIT. It adds 72 tokens to every session and 1,797 once invoked, about $0.0004 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 skills, from other repositories
boss-advanced
Advanced Boss orchestration patterns — Agent Teams leadership, 6-section delegation template, Skill vs Agent conflict resolution, Guardian pattern, and AI-slop detection.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
briefing-vault
Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.
manage-skills
세션 변경사항을 분석하여 검증 스킬 누락을 탐지합니다. 기존 스킬을 동적으로 탐색하고, 새 스킬을 생성하거나 기존 스킬을 업데이트한 뒤 CLAUDE.md를 관리합니다.
release
Bump package.json version and create a git tag for npm release. Accepts semver bump type (patch/minor/major) or explicit version.