Borrowing it
Nothing to install: this file belongs to martinambrus/haive. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/martinambrus/haive/main/AGENTS.mdgit clone --depth 1 https://github.com/martinambrus/haiveWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/martinambrus/haive/agents-md)<a href="https://agentmods.dev/instructions/martinambrus/haive/agents-md"><img src="https://agentmods.dev/badge/instructions/martinambrus/haive/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.20162 | $0.20162 |
| Opus 5 | $0.10081 | $0.10081 |
| Sonnet 5 | $0.04032 | $0.04032 |
| Haiku 4.5 | $0.02016 | $0.02016 |
Grade A, and why
haive AGENTS.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- clawker (Apache 2.0 Go binary) wrapped via child_process in `sandbox/clawker-client.ts`. The binary is installed only when the worker image is built with `CLAWKER_RELEASE_URL` plus a matching `CLAWKER_SHA256`; nothing How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Haive
Deterministic multi-CLI orchestration and AI agentic workflow utility. Reimplements a legacy markdown-driven Claude Code workflow, the autonomous /workflow implementation loop, and a sandboxed local environment replication step set as a deterministic web project. Agentic CLI invocations only happen for parts that genuinely need reasoning. Everything else runs as TypeScript step modules with web forms.
The legacy markdown step content has been ported into TypeScript step modules under packages/worker/src/step-engine/steps/. The original source archive is no longer vendored in the repo.
Stack
- pnpm workspace monorepo, turborepo
- Node 26, TypeScript 5.7, ES2024 target, NodeNext modules
- Hono 4 REST API on port 3001
- Next.js 16 + React 19 + Tailwind 4 web UI on port 3000
- Drizzle ORM on PostgreSQL 18, postgres.js driver
- BullMQ on Redis 8 (noeviction policy is required)
- Uploaded repo archives live in the
haive_reposnamed volume (shared by api and worker); Mailpit for dev SMTP - Docker Compose orchestrates everything; the dev stack is driven by
scripts/dev.sh(aliasedpnpm docker:dev), which wrapsdocker compose upwith the dev override and GPU layering - clawker (Apache 2.0 Go binary) wrapped via child_process in
sandbox/clawker-client.ts. The binary is installed only when the worker image is built withCLAWKER_RELEASE_URLplus a matchingCLAWKER_SHA256; nothing in this repo sets either, so the binary is absent from the shipped image and the wrapper is inert until someone wires it
Monorepo layout
haive/
package.json pnpm workspace root
pnpm-workspace.yaml
turbo.json
tsconfig.base.json
docker-compose.yml postgres, redis, mailpit, api, worker, web
docker-compose.dev.yml dev override: port exposure, hot reload, db-migrate one-shot
packages/
shared/ @haive/shared types, schemas, crypto, config, logger
database/ @haive/database Drizzle schema and migrations
api/ @haive/api Hono REST + WebSocket terminal proxy
worker/ @haive/worker BullMQ workers, step engine, sandbox manager, CLI adapters
web/ @haive/web Next.js Conductor-style UI
tests/
e2e/ Playwright specs
fixtures/
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 511 lines · 20,162 tokens per session scan A 7e807261f384
haive AGENTS.md is an instructions file published in the GitHub repository martinambrus/haive (5 stars, last pushed 2d ago), licensed MIT. It adds 20,162 tokens to every session, about $0.1008 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.