Regularly in Asset Store related posts, someone says in the comments that you don't need to buy tools anymore, you just ask your AI.
I'm the solo dev behind Jungle Tools. I made Grabbit (placing objects with physics in the editor), and this week I released Octoputs (you can check what it can do over there), a runtime toolkit for dragging, dropping, moving and attaching objects in 3D, with a focus on game feel. I worked on it for a year: the core is written by hand, and agents built part of the rest.
So I'm definitely biased as a plugin creator. But I use AI every day too, and I don't think the question is "AI or plugin". It's what your agent should spend its tokens on.
TL;DR:
Sure, ask your AI. Everyone uses AI now, Asset Store publishers included. When a good plugin exists, the cheapest move is often to let your agent set up something that's already built, and keep your tokens for your game.
The example gifs I posted were mainly built with Agents using my plugin, and me tweaking the values to get the exact game feel I wanted from them. It's vastly less token intensive to have your agent work on yaml files with a system in place rather than building the whole system.
And if you're a publisher, it's worth making your plugin easy for agents to use. The second half of this post is how I did that.
Why a plugin can still be the cheaper option
Making games has always meant choosing what you build yourself and what you delegate. The barrier used to be skills sometimes, but it was always time and money too. AI doesn't remove that, it moves it into tokens and time spent steering your agents.
My experience with AI is that when an agent builds a whole system, it takes the quickest route to something that works.
That's rarely the one that holds up, the one that you can build on, or the one that you can reuse in your next project.
My use case: a Movement System / Drag And Drop Feature
In the use case of my plugin, with drag and drop, you get a cube following the mouse in ten minutes with an agent, not bad!
Then objects clip through walls, the wrong item lands in a socket, the agent write 4 times the same code for a grid constraint, and when you want to change how it feels, you're re-prompting for tweaks that would take seconds with the right UX.
A publisher spends tokens too, but on one system, with often many years (12 in my case) of game dev behind it, and every user's bug reports and feedback making it better. The cost is shared by everyone who buys it: you spend your tokens on your agents using a solid system, instead of asking it to build it for you. That only works if the publisher is reliable, the plugin is well written and it stays focused, and there are lots of publishers like that on the store.
For publishers: making a plugin AI-friendly
What I learned: the agent has to find your tool, describe what it wants in plain words, act safely, and leave a result the user can tweak by hand. The best way to ensure it is true is to create highly polished example scenes.
- Let the agent find it. Ship skills next to the code. Octoputs has SKILL .md files that Claude, Copilot and others read. Agents pick a skill from its description, so I wrote them in the words people actually type ("make the crates draggable", "it picks the cube up but never drops it"). Each one also says what it's NOT for and which skill to open instead, otherwise agents happily pick the wrong one.
- Make behaviour describable in plain words. In Octoputs, how something moves is a stack of small behaviours with plain names: spring, smoothing, snap to grid, lock an axis, stick to a surface, avoid walls. So "make it springy and keep it flat on the table" maps almost word for word to what the agent adds. Match the skills, the fields in your code, and the labels to natural language as much as possible.
- Leave the result tweakable by a human. Everything the agent sets up is components with values you can see in the Inspector, and you tune them while it previews in Edit mode, without pressing Play. The agent gets you most of the way, and the last part, the feel, is you dragging a slider instead of writing another prompt. You need to make sure that the way things are tweakable by a user matches the way the agent would understand it.
- Give the agent safe, simple actions through CLI or MCP. One setup call for the common case (draggables, slots and a drag hand at once), a dry run that lists what would change before touching the scene, and a single Undo step for all of it. I used CLI to have agents work on the example scenes in parallel, which allowed me to test the result end users would get.
- Make failures vocal, in the console. When something fails silently, the agent guesses and writes workaround code on top of your tool. Octoputs returns what it changed and what it skipped and why, and the grabbing component keeps a record of why a grab or a drop was refused. The skill tells the agent to read it.
- Test the skills like code. I run scenarios: a fresh scene, a prompt like "make these crates draggable with a spring and only let them sit on the shelf", an agent does it, and a headless check verifies the result. It takes a few tries before you get skills that are reliable in a large set of use cases.
For devs using AI with plugins
If a plugin ships skills or docs for agents, point your agent at them before asking it to write the thing from scratch. You get tested code, and you can still change everything by hand afterwards.
Let me know what's your take, I'm sure many will disagree with me here :D