Borrowing it
Nothing to install: this file belongs to muratgur/ordinus. 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/muratgur/ordinus/master/AGENTS.mdgit clone --depth 1 https://github.com/muratgur/ordinusWrote 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/muratgur/ordinus/agents-md)<a href="https://agentmods.dev/instructions/muratgur/ordinus/agents-md"><img src="https://agentmods.dev/badge/instructions/muratgur/ordinus/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/muratgur/ordinus/agents-md"><img src="https://agentmods.dev/badge/instructions/muratgur/ordinus/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01112 | $0.01112 |
| Opus 5.5 | $0.00445 | $0.00445 |
| Sonnet 5.5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
ordinus AGENTS.md scanned grade A with 0 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 2mo ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ordinus Agent Guide
Mission
Ordinus is a desktop workspace for coordinating AI agents around real software work. Keep the product simple, observable, local-first, and user-controlled.
Build a command center for AI-assisted work, not a generic chatbot.
Product Principles
- Make agent activity visible: planned, running, blocked, completed.
- Give agents clear roles and responsibilities.
- Help agents coordinate instead of running disconnected conversations.
- Keep the user in control of important actions.
- Prefer a small reliable workflow over broad unfinished features.
- Avoid integrations before the core runtime model is stable.
Architecture Direction
- Electron main process owns privileged work: filesystem, database, process execution, provider runtimes, and OS integration.
- Renderer is UI only. It must not access Node, filesystem, child processes, secrets, or SQLite directly.
- Preload exposes only a small typed
window.ordinusAPI. - Never expose raw
ipcRenderer,electron, filesystem, process, or database APIs to renderer code. - Provider runtime must follow
docs/provider-runtime-contract.mdbefore adding CLI detection or process spawning. - Provider commands use executable plus args, not raw shell strings.
- Runtime environment is deny-by-default; secrets are referenced, resolved in main, and never logged.
- Shared contracts live in
src/shared. - Use SQLite for durable app state, but add tables only when the product model is clear.
- Keep SQLite schema changes in Drizzle migrations under
app/resources/db/migrations. - Run migrations from the Electron main process before registering IPC handlers.
- Track applied SQL through Drizzle and app-level schema version through
app_meta.schema_version. - Do not add agent, task, provider, schedule, or inbox schemas prematurely.
Cross-Platform Development
Ordinus must work on both macOS and Windows. When making changes, account for platform differences before finishing.
- Do not assume POSIX-only paths, shell commands, environment variable syntax, executable names, file permissions, or case-sensitive filesystems.
- Use Node/Electron APIs such as
path,os, and provider commandexecutable + argsarrays instead of shell-specific strings. - Consider Windows
.cmd/.exebehavior, spaces in paths, CRLF/LF differences, and macOS/Linux case sensitivity. - For changes touching filesystem access, process execution, packaging, provider runtimes, scripts, or native dependencies, verify or explain platform impact.
- Prefer npm scripts and cross-platform tooling over shell-specific commands.
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.
- 2mo ago First seen · 114 lines · 1,112 tokens per session scan A 386f05d22497
ordinus AGENTS.md is an instructions file published in the GitHub repository muratgur/ordinus (114 stars, last pushed 1mo ago), licensed MIT. It adds 1,112 tokens to every session, about $0.0044 per session on Opus 5.5. A static security scan graded it A with 0 findings. 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.