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 skills add DavidROliverBA/ArchitectKB --skill screenshot-analyzegit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/screenshot-analyze)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/screenshot-analyze"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/screenshot-analyze/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/skills/davidroliverba/architectkb/screenshot-analyze"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/screenshot-analyze.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.00000 | $0.00694 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
screenshot-analyze 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/screenshot-analyze
Perform comprehensive analysis of screenshots using Sonnet sub-agents for detailed visual inspection.
Usage
/screenshot-analyze <image-path>
/screenshot-analyze +Attachments/error-screenshot.png
/screenshot-analyze +Attachments/ui-mockup.png --context "login flow"
Instructions
This skill uses Sonnet model sub-agents for thorough image analysis with vision capabilities.
Phase 1: Image Loading
- Verify the image exists at the specified path
- Check file type is supported (PNG, JPG, JPEG, GIF, WebP)
- Note any context provided by user
Phase 2: Comprehensive Analysis (Sonnet Sub-Agents)
Launch these sub-agents using model: "sonnet":
Agent 1: Content Extraction (Sonnet)
Task: Extract all visible content from the image
- Read the image file using the Read tool
- Extract all visible text (OCR)
- Identify UI elements, buttons, labels
- Note any error messages or notifications
- Capture data values, IDs, or codes visible
Return: Complete text extraction with location context
Agent 2: Visual Structure Analysis (Sonnet)
Task: Analyse the visual structure and layout
- Read the image file
- Identify the type of content (UI, diagram, document, error, etc.)
- Map the visual hierarchy and layout
- Note colour schemes, branding elements
- Identify interactive elements
- Assess visual quality and clarity
Return: Structural analysis with element inventory
Agent 3: Context & Purpose Analysis (Sonnet)
Task: Understand the purpose and context
- Read the image file
- Determine what application/system is shown
- Identify the workflow or process stage
- Note any problems or issues visible
- Assess what action might be needed
- Connect to known YourOrg systems if recognisable
Return: Contextual interpretation with system identification
Phase 3: Compile Report
# Screenshot Analysis
**Image**: {{filename}}
**Analysed**: {{DATE}}
**Type**: {{UI/Error/Diagram/Document/Other}}
## Summary
{{2-3 sentence overview of what the image shows}}
## Extracted Content
### Text Found
{{all readable text, organised by location}}
### UI Elements
| Element | Type | Label/Text | State |
|---------|------|------------|-------|
{{element inventory}}
### Data Values
{{any IDs, codes, numbers, or data visible}}
## Visual Analysis
### Layout Structure
{{description of visual hierarchy}}
### Application/System
- **Identified as**: {{system name if known}}
- **Screen/Page**: {{specific view or page}}
- **Context**: {{workflow stage}}
## Observations
### Key Findings
{{important observations}}
### Issues Detected
{{any errors, warnings, or problems visible}}
### Recommendations
{{suggested actions based on analysis}}
## Related Notes
{{suggest links to related vault notes if system is recognised}}
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.
- 9d ago First seen · 123 lines · 0 tokens per session scan A 069320613b1e
screenshot-analyze is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 tokens. 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-09-03.
Other skills, from other repositories
html-ppt-zhangzara-block-frame
Rescuing a messy startup deck into a board-grade system — the diagnosis, the page grammar, and the rebuilt proof pages. Built as a decision-grade design craft deck for founders, exec presenter.
accesslint-scan
Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.
check
Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.
health
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…
hunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…
think
Turns rough ideas into approved, decision-complete plans with validated structure before coding. Use when users ask in any language for planning, architecture, design direction, feasibility, value judgment, or whether a feature is worth doing before implementation. Not for bug fixes or small edits.