cd /news/ai-agents/the-toolsmith · home › topics › ai-agents › article
[ARTICLE · art-171309] src=blog.fsck.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

The Toolsmith

Jesse Vincent, creator of RT and the Superpowers project, released toolsmith, a plugin for coding agents that hands tool-building work to a dedicated subagent rather than letting the primary session create incidental scripts. The toolsmith subagent maintains a git repository at ~/.local/share/toolsmith/tools cataloging general-purpose and per-project tools, creating new ones on request or extending existing ones, and Vincent reports it has built dozens of small tools over a couple of weeks, from HTML word counters to managers for fleets of ephemeral EC2 instances.

key takeaway

Route tool-building to a dedicated toolsmith subagent that stores reusable scripts in a shared git catalog at ~/.local/share/toolsmith/tools, so the primary session reuses or extends existing tools instead of rebuilding them in ephemeral scratch directories.

read3 min views1 publishedNov 17, 2026

I was a sophomore in college the first time I read Fred Brooks's The Mythical Man-Month. If you're involved in the production of software and haven't read it, you should probably fix that. But I bet you have. You've certainly been exposed to its memes. For example, it's the source of Brooks's Law: "Adding manpower to a late software project makes it later."

The book also laid out Harlan Mills's proposal for organizing a large software project into well-defined "Surgical Teams" with a chief programmer, a copilot, a "program clerk" who maintains records, a "language lawyer" who knew the ins and outs of the compiler and chosen programming language, and a toolsmith who was responsible for building and maintaining bespoke tooling to let the chief programmer and their copilot stay focused on the primary mission.

As soon as I read that, I knew I wanted to be a toolsmith. In a lot of ways, the toolsmith mentality has defined my career. Building RT, a tool to help teams track what needs doing led directly to my time as the project lead for Perl 5. In that era, Perl was the epitome of a tool for building more tools. Keyboardio built the physical tools many folks use to practice their craft. And in terms of building tools that help millions(!) of people build software, Superpowers has succeeded beyond my wildest dreams.

But this isn't supposed to be me writing about my role as a toolsmith for the internet.

One of the patterns that I baked into my AGENTS.md file pretty early was the idea that if you're going to do something once, you're probably going to do it twice, so you should write a script, rather than just run commands by hand. And my agents were more than happy to comply. But they were building those tools as incidental work on their way somewhere else and dropping them into ephemeral scratch directories.

As someone who's known for ranting about how important it is to make sure your agents are decomposing their tasks and handing only a single mission to a given agent, I'm embarrassed by how long it's taken me to come around to realizing that "write a script to automate this task" is a separable mission and deserves an agent's exclusive focus.

So a couple weeks back, I sat down and specced out the first version of toolsmith, a plugin for your favorite coding agent.

It teaches your primary session that instead of building incidental tools itself, it should hand that work off to a toolsmith subagent. You can think of that subagent as something like a digital version of James Bond's Q. It's responsible for building, maintaining, and cataloging all of the weird, bespoke tools that help your agent get its work done.

On the backend, it maintains a git repository in ~/.local/share/toolsmith/tools. Inside that repo is a catalog of general-purpose tools it has built, as well as a catalog of project-specific tools for each of your various projects. Any time a session reaches for a tool that's been built before, it's close at hand. If an agent asks for a tool that doesn't exist, the toolsmith will create it. If there's a tool that's already close, the toolsmith will extend it for your agent.

I've had the toolsmith running for a couple of weeks now and it has created dozens of small tools for my agents. Looking through my tools directories, I see everything from a tool to count words in an HTML document to a tool to find iOS device IDs to tools to make RPC calls to some internal products to a tool to manage fleets of ephemeral EC2 instances.

I'd love to hear about what your agents' new toolsmith builds for you.

── more in #ai-agents 4 stories · sorted by recency
── more on @jesse vincent 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/the-toolsmith] indexed:0 read:3min 2026-11-17 · —