Skip to content

srinitude/agentix

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Agentix

My agentic toolbox. Batteries included. Node.js excluded.

┌─────────────────────────────────────────────────────────────┐
│  "What if coding agents were opinionated about everything?" │
└─────────────────────────────────────────────────────────────┘

Supported Agents

Agent Status Notes
Claude Code ✅ Supported Full integration
Droid 🔜 Planned
Cursor 🔜 Planned
Codex 🔜 Planned
Opencode 🔜 Planned
Gemini CLI 🔜 Planned
Goose 🔜 Planned
Kilocode 🔜 Planned
Aider 🔜 Planned
Cline 🔜 Planned

What's in the box?

.claude/
├── agents/           # The workforce
│   ├── idea-scaffolder.md    → Builds specs through interrogation
│   └── skill-generator.md    → Creates skills that create skills
│
├── skills/           # The slash commands
│   ├── generating-skills/    → /generating-skills - meta as it gets
│   └── scaffolding-ideas/    → /scaffolding-ideas - death by questions
│
├── settings.json     # The rules
│   ├── hooks         → Bun or bust
│   ├── permissions   → Trust but verify
│   └── deny list     → node? npm? npx? lol no
│
└── settings.local.json       # The secrets (gitignored)

Philosophy

One runtime to rule them all. This repo enforces Bun exclusively. Try to run node or npm and watch the hooks stop you cold:

HOOK BLOCKED: Node.js command detected. IMMEDIATELY retry with bun equivalent:
  node script.js → bun script.js
  npx package → bunx package
  npm run X → bun run X

Write code with Node.js imports? The pre-write hook has opinions about that too.

Skills

/generating-skills

A skill that generates skills. Yes, it generated parts of itself.

/generating-skills reviewing-code --depth=standard

Creates a complete skill scaffold:

  • SKILL.md with proper frontmatter
  • manifest.json for machines
  • examples/ for humans
  • Validation that actually validates

/scaffolding-ideas

For when you need to think harder. Uses gated phases to force you through structured ideation:

/scaffolding-ideas a distributed cache invalidation system

Then answer questions until you've accidentally written a complete spec. Uses Exa and Firecrawl for research-backed validation because your assumptions are probably wrong.

Gate phrase to advance: This is the perfect spec for this phase! Go to the next question section

Gate phrase to escape: This is the perfect scaffolding

Agents

Agent Purpose Vibe
idea-scaffolder Elicits specifications through relentless questioning Socratic method meets product manager
skill-generator Creates new skills with proper structure Recursive self-improvement

Hooks

Pre-tool-use hooks that enforce the Bun-only policy:

Tool Hook Effect
Bash Blocks node/npm/npx Suggests bun equivalents
Edit Validates imports No fs, no path, no Node.js
Write Validates imports Same deal

Permissions

Allowed: Everything useful (Read, Write, Bash, MCP tools, etc.)

Denied:

  • sudo (obviously)
  • rm -rf / (nice try)
  • .env files (secrets stay secret)
  • Every Node.js package manager ever invented

Setup

# Clone it
git clone <this-repo> agentix
cd agentix

# Install deps (with bun, obviously)
bun install

# Copy env and add your keys
cp .env.example .env.local

# Validate all skills
bun run validate:all

# Check for forbidden Node.js imports
bun run check:node

Environment Variables

Variable Required Purpose
EXA_API_KEY For research Semantic search via Exa
FIRECRAWL_API_KEY For research Web scraping via Firecrawl

Without these, /scaffolding-ideas works but can't validate assumptions against the real world.

Scripts

bun run validate        # Validate a skill
bun run validate:all    # Validate all skills
bun run check:node      # Find Node.js imports (and judge them)
bun run typecheck       # TypeScript without the runtime

MCP Integrations

Configured for:

  • mcp__exa__* — Semantic search for research
  • mcp__firecrawl__* — Web scraping for documentation

The Meta Layer

This repo is self-documenting, self-validating, and mildly self-aware:

  1. Skills validate themselves via validate-skill.ts
  2. Hooks enforce the rules that hooks are written in
  3. The generating-skills skill can update itself
  4. The scaffolding-ideas skill was scaffolded by scaffolding-ideas

It's agents all the way down.

Roadmap

Soon™
──────
[ ] /git                 → Commit workflow that follows conventions (you have one, right?)
[ ] /reviewing-code      → Opinionated code review. Your code has opinions about itself.

Later™
──────
[ ] /refactoring         → Guided refactoring with before/after validation
[ ] /debugging           → Hypothesis-driven investigation. Socratic method for stack traces.
[ ] /testing             → Test generation that understands your patterns
[ ] /migrating           → Schema/API/dependency migrations without the tears

Eventually™
───────────
[ ] /researching         → Deep technical research via Exa/Firecrawl
[ ] /benchmarking        → Performance testing with Bun's built-in benchmarking
[ ] /analyzing-deps      → Security audit, bundle impact, "why do I have 847 packages"
[ ] /hooking             → Meta-skill to generate hooks. Hooks generating hooks.
[ ] /prompting           → Prompt engineering. Prompts about prompts.

...and more...

About

My agentic toolbox. Batteries included. Skills, agents, and hooks for coding agents.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published