After many personal peaks and troughs, and with much AI assistance, I was finally able to put something into the world for the first time that represented some of the ideas I've had over the last 6 months.

Packs are essentially plugins, but harness-agnostic. aipack is a CLI that can sync packs into harness-specific locations/formats. What makes this different are the profiles: profiles are parameterized collections of packs that are essentially declarative agents with sets of rules, skills, workflows, MCP, and sub-agents. You can create a personal profile that layers packs from different sources on top of each other, selectively enabling resources from each pack until you have a the exact mix of resources you want in your agent.

I've experimented with many harnesses and agents in my explorations of the tech, and I always found that myself wishing for a canonical format and location to share resources across harnesses. I also wanted to have a proper place to put org/team specific content I was working on, and for it to be importable regardless of the harness the user/engineer happened to use. So I built aipack in a fit of vibe-coding fervor.

It's not perfect, It's a mess in places (so am I), but it gets the job done. Members of my team are excited about it, and other teams are beginning to convert their un-organized rules/skills/etc. into pack format, and that means a lot to me.

The thing I haven't gotten is real, public perspective and feedback. If you think this has a place potentially as the next layer of AI configuration abstraction, please share your thoughts. If you have valid critique of my post, the tool I built, or the pack ecosystem I'm envisioning, please share that too.

Best, David