Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/zvadaadam/deus-machine/agents-mdgit clone --depth 1 https://github.com/zvadaadam/deus-machineWrote 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/zvadaadam/deus-machine/agents-md)<a href="https://agentmods.dev/instructions/zvadaadam/deus-machine/agents-md"><img src="https://agentmods.dev/badge/instructions/zvadaadam/deus-machine/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 | $0.02922 | $0.02922 |
| Opus 5 | $0.01461 | $0.01461 |
| Sonnet 5 | $0.00584 | $0.00584 |
| Haiku 4.5 | $0.00292 | $0.00292 |
Grade C, and why
deus-machine AGENTS.md scanned grade C with 2 findings 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 today.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://bun.sh/install | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://bun.sh/install | bash How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deus Machine
IDE for managing multiple parallel AI coding agents. Built for semi-technical people who care about output, not the code underneath. AI chat is the first-class citizen, code is secondary.
Design inspiration: Linear, Vercel, Stripe, Perplexity. Dense, pro-consumer aesthetic.
Tech Stack
Electron desktop app + React frontend + Node.js backend. Monorepo under apps/.
- Package manager: Bun. Always
bun add,bun install,bun run,bunx. Never npm or yarn — CI usesbun install --frozen-lockfile. - Desktop + Mobile Web: Primary target is Electron. Web version lives at the root domain (
deusmachine.ai— the landing worker edge-routes/to the landing for new visitors and everything else to the app;app.deusmachine.aistays a working alias (canonical 301 configured at the edge)) and also supports mobile viaMobileLayout. Don't writeisElectronEnvconditionals for feature parity. - Key libraries:
ts-patternfor discriminated unions (prefer.exhaustive()), Zustand for UI state, TanStack Query v5 for server state, Framer Motion for presence/layout animations, Tailwind CSS v4.
Running the App
bun run dev:web # Web: backend + frontend (dev.sh)
bun run dev # Desktop: Vite + backend + Electron
Never run bun run dev:frontend alone — it skips the backend.
- Frontend: http://localhost:1420 (Vite auto-increments if taken)
- Backend: dynamic port (check terminal output)
Cursor Cloud setup
Fresh cloud images should have Bun available. If command -v bun fails, install it before any repo commands:
curl -fsSL https://bun.sh/install | bash
export PATH="$HOME/.bun/bin:$PATH"
For a fresh cloud agent, set up and smoke-test the repo from the workspace root:
bun install --frozen-lockfile
bun run typecheck
bun run test:backend
bun run test:agent-server
bun run dev:web
bun run dev:web is the preferred cloud smoke because it rebuilds the Node native module ABI, starts the backend, lets the backend own agent-server startup, and then starts Vite with the emitted backend port. Confirm the terminal shows [agent-server] LISTEN_URL=..., [BACKEND_PORT]..., Server ready!, and [AgentService] Connected, agents: [claude, codex-sdk, codex-server] before opening the frontend URL.
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.
- today Changed · +47 tokens per session d72c448ad43a
- 4d ago First seen · 215 lines · 2,875 tokens per session scan C b3175903dd6d
deus-machine AGENTS.md is an instructions file published in the GitHub repository zvadaadam/deus-machine (24 stars, last pushed today), licensed MIT. It adds 2,922 tokens to every session, about $0.0146 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.