Hermes Plugins (42-evey) - Setup Guide¶

Native Hermes Agent plugins by 42-evey. Provides goals tracking, inter-agent communication bridges, model selection routing, and cost control - four missing primitives for production Hermes deployments.

What It Provides¶

Goals tracking - define, track, and report on agent goals with completion gates
Inter-agent bridge - structured communication between Hermes agents without shared memory
Model selection - automatic model routing based on task complexity and cost budget
Cost control - token usage caps, per-task budgets, and spending alerts

Installation¶

# Install via skills.sh
npx skills add https://github.com/42-evey/hermes-plugins

# Manual clone
git clone https://github.com/42-evey/hermes-plugins.git ~/.hermes/skills/hermes-plugins-42evey

Configuration¶

Goals Plugin¶

goals:
  enabled: true
  storage: "~/.hermes/goals.json"
  max_active: 5
  auto_archive: true

Inter-Agent Bridge¶

bridge:
  enabled: true
  protocol: "stdio"       # or "http" for remote agents
  peer_agents:
    - name: "dev-hermes"
      endpoint: "http://agent-a.local:9090"
    - name: "ops-hermes"
      endpoint: "http://agent-b.local:9090"
  auth_token: "${BRIDGE_AUTH_TOKEN}"

Model Selection¶

model_selector:
  enabled: true
  default_model: "sonnet"
  routing_rules:
    - pattern: "refactor|debug|test|build"
      model: "sonnet"
    - pattern: "research|strategy|architecture|board"
      model: "opus"
    - pattern: "social|post|tweet|reddit"
      model: "sonnet"
    # Never route to haiku
  cost_budget_daily: 50.00   # USD

Cost Control¶

cost_control:
  enabled: true
  daily_budget: 50.00         # USD
  per_task_budget: 5.00
  alert_threshold: 0.80       # alert at 80% of budget
  block_on_exceeded: true     # hard stop when budget exceeded

Key Workflows¶

Set and track a goal¶

/hermes-plugins goal-create "Deploy CorpusIQ MCP server to production"
/hermes-plugins goal-status

Send a task to another agent¶

/hermes-plugins bridge-send dev-hermes "Run the test suite on the latest PR"

Check cost status¶

/hermes-plugins cost-status

Verification¶

# Test plugins load
hermes skills list | grep hermes-plugins

# Test goals plugin
hermes chat -q "/hermes-plugins goal-list"

# Test bridge
hermes chat -q "/hermes-plugins bridge-status"

Pitfalls¶

Bridge auth tokens: Store in environment variables, never in config files. The BRIDGE_AUTH_TOKEN is read from the environment at plugin load time.
Cost tracking accuracy: Model costs are estimated based on published pricing. Actual costs may differ with provider-specific discounts or surcharges.
Goal storage: JSON file storage can corrupt on concurrent writes from multiple agent sessions. For production, consider migrating to SQLite.
Inter-agent loops: Ensure bridge communication doesn't create infinite loops (A sends to B, B sends to A). The bridge has a max_depth: 3 default.

Integration with CorpusIQ¶

CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.

This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.

See what CorpusIQ connects