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/ihatesea69/kiro-kit/ai-multimodalnpx skills add ihatesea69/kiro-kit --skill ai-multimodalgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/ai-multimodal)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/ai-multimodal"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/ai-multimodal.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.1 | $0.00029 | $0.00240 |
| Opus 5 | $0.00015 | $0.00120 |
| Sonnet 5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
ai-multimodal 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 6d 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
AI Multimodal
Activate this skill when processing or generating multimedia content.
When to Use
- Analyzing images or screenshots
- Processing audio files (transcription, summarization)
- Extracting data from documents (PDF, forms)
- Generating images from text prompts
- Processing video content
Capabilities
- Image analysis: captioning, OCR, object detection, visual Q&A
- Audio processing: transcription with timestamps, summarization
- Document extraction: tables, forms, charts from PDFs
- Image generation: text-to-image, editing, composition
- Video analysis: scene detection, temporal analysis
Rules
- Use appropriate model for the task (vision vs audio vs generation)
- Respect file size limits for each API
- Handle processing errors gracefully
- Validate output quality before using results
- Consider privacy implications of media processing
What ships with it
13 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.
- .env.example 3.7 KB
- references/audio-processing.md 9.2 KB
- references/image-generation.md 13 KB
- references/video-analysis.md 11 KB
- references/vision-understanding.md 10 KB
- scripts/document_converter.py 12 KB runs code
- scripts/gemini_batch_process.py 16 KB runs code
- scripts/media_optimizer.py 16 KB runs code
- scripts/requirements.txt 442 B
- scripts/tests/requirements.txt 352 B
- scripts/tests/test_document_converter.py 2.2 KB runs code
- scripts/tests/test_gemini_batch_process.py 12 KB runs code
- scripts/tests/test_media_optimizer.py 12 KB runs code
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.
- 6d ago First seen · 41 lines · 29 tokens per session scan A 53d8eb9f91c8
ai-multimodal is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 17d ago), licensed MIT. It adds 29 tokens to every session and 240 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-30.
Other skills, from other repositories
bedrock-guardrails
Audit the guardrail layer around Amazon Bedrock usage: region pinning and cross-region inference profiles, IAM scoping to model ARNs, Bedrock Guardrails configuration (PII, denied topics, content and word filters, grounding, versioning), invocation logging and KMS, per-tenant isolation, prompt injection boundaries…
kb-review
Read-only review of a retrieval-augmented setup, Amazon Bedrock Knowledge Bases first and hand-built RAG pipelines second: sources, chunking, metadata and tenant filtering, embedding model, vector store, sync, retrieval quality and cost per query. Builds a golden question set, measures recall@5 and MRR against the…
connect-review
Review an Amazon Connect contact-center solution built on Lex bots and Bedrock-backed conversational logic: contact flows, bot design, Lambda integrations, prompts, latency budget, state handling, observability and cost per contact. Produces a severity-ranked findings report with a latency table, a cost estimate and…
ai-cost-guard
Find every code path that can run up a paid-inference bill without a ceiling (loops, retries, fan-out, agent steps, queues) and require a written dollar cap both in code and at the provider. Use before shipping anything that calls an LLM, speech, or image API, or when a bill was larger than expected.
ecs-genai
Use whenever someone runs a GPU / ML / GenAI / LLM workload on Amazon ECS: GPU on ECS, ECS GPU-optimized AMI, g4dn/g5/g6/p4/p5 on ECS, which ECS launch type for GPU, Inferentia/Trainium/Neuron on ECS, distributed training, model inference or vLLM/Triton/TGI/Ray on ECS, Capacity Blocks, GPU sharing, ASG per GPU type.…
eks-genai
Use whenever someone is building, training, fine-tuning, or serving a generative AI / LLM workload on Amazon EKS — phrased as "GPU vs Trainium/Inferentia", "vLLM on EKS", "Ray Serve / KubeRay", "distributed training on EKS", "FSx for Lustre for ML", "Karpenter for GPU", "EFA / NCCL multi-node", "DCGM / Neuron…