Borrowing it
Nothing to install: this file belongs to minnhaaaaa/civitas. 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/minnhaaaaa/civitas/main/AGENTS.mdgit clone --depth 1 https://github.com/minnhaaaaa/civitasWrote 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/minnhaaaaa/civitas/agents-md)<a href="https://agentmods.dev/instructions/minnhaaaaa/civitas/agents-md"><img src="https://agentmods.dev/badge/instructions/minnhaaaaa/civitas/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.09330 | $0.09330 |
| Opus 5 | $0.04665 | $0.04665 |
| Sonnet 5 | $0.01866 | $0.01866 |
| Haiku 4.5 | $0.00933 | $0.00933 |
Grade A, and why
civitas 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 5d 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 — 1,912 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project
Civitas — Autonomous Food Procurement through Agent Parliament and Agent Jury
Civitas is a multi-agent autonomous procurement system based on Problem Statement 5 of the AgentXcelerate challenge.
The official problem asks the system to determine what food to procure, how much to procure, from which suppliers, and how inventory should be distributed across locations while considering demand, inventory, supplier lead times, pricing, perishability, and location requirements.
Civitas goes beyond this baseline by introducing:
- Agent Parliament — autonomous agents with conflicting objectives negotiate a procurement plan.
- Agent Jury — evaluates whether the reasoning and evidence behind the agreement deserve to be trusted.
- Adaptive Replanning — a weak Jury result sends the system back into investigation and negotiation instead of allowing immediate execution.
1. Core Product Principle
Don't just make agents agree. Make sure their agreement deserves to be trusted.
The system must distinguish:
Agent Agreement
≠
Independent Evidence
≠
Correct Decision
A proposal supported by six agents can still be based on one underlying source or one propagated assumption.
Civitas therefore treats evidence lineage as a first-class object.
2. Architecture
The primary control loop is:
USER GOAL
↓
PLANNER
↓
PARLIAMENT
↓
INVESTIGATION THROUGH MCP
↓
COMPETING PROPOSALS
↓
NEGOTIATION
↓
CANDIDATE PLAN
↓
JURY
↓
┌───────────────┐
│ │
▼ ▼
APPROVE INVESTIGATE
│ │
▼ ▼
EXECUTE REPLAN
│
└──────→ PARLIAMENT
The Jury is therefore part of the autonomous planning loop.
It is not a final dashboard or post-hoc evaluator.
The primary product interface is conversational:
OPERATOR → CODEX → CIVITAS MCP SERVER → CONTROL LOOP
→ OPERATIONAL MCP PROVIDERS
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.
- 5d ago First seen · 1,912 lines · 9,330 tokens per session scan A 9f79d8620ba2
civitas AGENTS.md is an instructions file published in the GitHub repository minnhaaaaa/civitas (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 9,330 tokens to every session, about $0.0466 per session on Opus 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-31.
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.