Borrowing it
Nothing to install: this file belongs to vulnmaster/CASE-UCO-SDK. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vulnmaster/CASE-UCO-SDK/main/.cursor/skills/image-to-case-uco/SKILL.mdgit clone --depth 1 https://github.com/vulnmaster/CASE-UCO-SDKWrote 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/vulnmaster/case-uco-sdk/image-to-case-uco)<a href="https://agentmods.dev/skills/vulnmaster/case-uco-sdk/image-to-case-uco"><img src="https://agentmods.dev/badge/skills/vulnmaster/case-uco-sdk/image-to-case-uco/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/vulnmaster/case-uco-sdk/image-to-case-uco"><img src="https://agentmods.dev/badge/skills/vulnmaster/case-uco-sdk/image-to-case-uco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01036 |
| Opus 5.5 | $0.00022 | $0.00414 |
| Sonnet 5.5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
image-to-case-uco 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 16d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Image To CASE/UCO
Workflow
-
Identify the image artifact:
- Record file path, file name, extension, MIME type, byte size, dimensions, and SHA256.
- Model the source image as
ObservableObjectwithFileFacetandContentDataFacet. - Use
ContentDataFacet(hash=[Hash(hash_method=["SHA256"], hash_value=...)]).
-
Extract text:
- Prefer a real OCR engine when available (
tesseract, cloud OCR, or an application OCR service). - If OCR is unavailable and the image is visible in the prompt, use vision-assisted transcription and mark that method in the graph.
- Preserve raw OCR text with
ExtractedStringsFacet(strings=[ExtractedString(...)])on the source image observable.
- Prefer a real OCR engine when available (
-
Analyze the content:
- Parse domain facts from OCR text, such as receipt totals, timestamps, merchant names, addresses, line items, payment methods, identifiers, or account fragments.
- Keep uncertain values in annotations or descriptions; do not overstate them as verified facts.
- Redact or preserve masked values as they appear. Never infer full payment card numbers, personal identifiers, or secrets from partial values.
-
Map to ontologies with the CASE/UCO MCP:
- Always read the MCP tool schema before calling a tool.
- Use
search_classes,find_classes_for_domain,guide_mapping, andget_class_detailsto select classes. - Use existing UCO/CASE/CAC classes first. If no adequate class exists, model source evidence plus extracted attributes using
Event,Annotation,Dictionary, or a documented local extension rather than inventing unvalidated terms.
-
Serialize:
- Use
CASEGraphand generated classes where possible. - Use UUID-ending IRIs so
case_validatedoes not emit identifier info findings. - For receipt-like images, a good baseline is:
- Source image:
ObservableObject+FileFacet+ContentDataFacet+ExtractedStringsFacet - Merchant:
Organization - Address:
Location+SimpleAddressFacet - Payment card fragment:
PaymentCardplus a conservative description orAccountFacet(account_identifier=masked_value) - Transaction facts:
Eventwithevent_contextreferences andevent_attribute=[ProperDictionary(...)] - Processing provenance:
InvestigativeActionwithinstrument=[Tool(...)],object=[source_image], andresult=[derived_event]
- Source image:
- Use
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.
- 16d ago Changed 1e63fa779a6f
- 1mo ago First seen · 87 lines · 54 tokens per session scan A 7a00158e3fcd
image-to-case-uco is a skill published in the GitHub repository vulnmaster/CASE-UCO-SDK (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,036 once invoked, about $0.0002 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 skills, from other repositories
parsing-artifacts-with-eric-zimmerman-tools
Parse registry, prefetch, shellbags, and MFT with EZ Tools and Timeline Explorer.
building-super-timelines-with-plaso
Generate log2timeline and Plaso super-timelines and triage them in Timesketch.
fleet-hunting-with-velociraptor
Deploy a Velociraptor server and agents and write VQL hunts across a fleet.
vhir-ingest
How to start an investigation once the evidence is surveyed: which tools to run first, ingesting evidence into OpenSearch (triage packages, memory, delimited files) and querying it. Use after the evidence survey, before analysis, or when ingesting or querying indexed evidence.
xways-xtension-authoring
This skill should be used when the user asks to "create/scaffold a new X-Tension", "wrap a CLI tool in an X-Tension", "port a convention into an X-Tension" (helper-exe verification, Ctrl-to-save, output-dir), "audit/modernize an X-Tension", "build/compile an X-Tension", "prep an X-Tension for public release", or asks…
building-super-timelines-with-plaso
Generate log2timeline and Plaso super-timelines and triage them in Timesketch.