The OpenAI batch API is pretty cool at 50% of the cost. Great for large scale tasks such as captioning 42k images with gpt-5-mini.
Here is what I learned:
1. there is an org-level cap of 5M enqueued tokens per model so you need to throttle the uploads to stay below that. Not sure why they don't take care of that internally;
2. each batch upload must be below 200MB of so I had to create 75 JSONL files (multiple JSON objects per line) for 42k images resized to 1536px on the long edge.
During the weekend I built a contextual search tool for a photo library with 42k images across 2.8k galleries. The results are amazing!
Turns out the AI models that generate embedding vectors from images directly are BAD at capturing the image contents, so I had to first generate captions and then generate the embeddings for the captions instead.
Total cost: $30 for both captions (gpt-5-mini) and embeddings (text-embedding-3-large with 3072 dimensions).
The FAIR standard (originally created for WordPress and built on AT protocol) would be perfect for distributing agent plugins since it covers everything from versioning, signing, discovery and packaging.
What do you think of these Claude system prompts? Sound a bit too verbose and as if AI was used to iterate on them which eventually flattens the intent and looses the nuance.
Thanks to the "Agent Skills Discovery via Well-Known URIs" RFC from Cloudflare we can have WordPress as the Skills CMS with the convenience of `npx skills add https://…`
I really hope we eventually arrive at an open package standard for bundling these custom AI plugins that can be self-hosted and installed using any AI GUI harness.
Currently all the nice AI things are mostly available to developers who can run CLI commands.
Check your AI tool memories (under ~/.codex/memories and ~/.claude/projects). I find that most of them are actually polluting the context and not helping.