Borrowing it
Nothing to install: this file belongs to adanb13/cirdan. 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/adanb13/cirdan/main/AGENTS.mdgit clone --depth 1 https://github.com/adanb13/cirdanWrote 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/adanb13/cirdan/agents-md)<a href="https://agentmods.dev/instructions/adanb13/cirdan/agents-md"><img src="https://agentmods.dev/badge/instructions/adanb13/cirdan/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/adanb13/cirdan/agents-md"><img src="https://agentmods.dev/badge/instructions/adanb13/cirdan/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.01466 | $0.01466 |
| Opus 5.5 | $0.00586 | $0.00586 |
| Sonnet 5.5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
cirdan 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on Cirdan
Cirdan is a Python package (cirdanops) providing the cirdan CLI and cirdand daemon. It is an on-call software repair agent: a production alert (Grafana / Alertmanager / Slack) resolves to a registered service and repo via the explicit services: registry in cirdan.yaml, the failure is reproduced in an isolated runner (Docker Compose / K8s), a coding agent fixes the code (an in-process API provider, or a workspace-spawned local agent CLI in the cli posture), the fix is re-verified against the pinned repro probe and the repo test suite, and a verified PR opens (@cirdan review loop; CI checks watched). When policy allows, delivery merges, deploys, and verifies production recovery, stopping at manual_required on failure.
Setup
python3 -m venv --without-pip .venv # ensurepip may be unavailable on Debian/Ubuntu
python3 -m pip --python .venv/bin/python install -e ".[all,dev]"
.venv/bin/python -m pytest tests/ -q
Architecture in one paragraph
cirdan.engine.CirdanEngine is the single wiring point used by the CLI (cirdan/cli/main.py), MCP server (cirdan/mcp/server.py), HTTP API (cirdan/api/http.py), and daemon (cirdan/daemon/server.py). It owns config (cirdan/config.py — the services: registry of ServiceEntry/DeployTargetConfig, routing policy, safety gates), the access context (a probed mirror of what the session can do — cirdan/access/), the SQLite store (cirdan/graph/store.py — one file holding incidents, alerts, events, agent runs, and kv state; a storage substrate, not topology), and the audit log. cirdan/registry.py is the source of truth for what is repairable: alert→service matching (match_alert), service→repo resolution (repairable_repo), and the typed runtime target (LiveTarget) consumed by probe exec, MCP get_logs/get_state, and the docker/kubernetes adapters. Alerts arrive through cirdan/ingest/, route through the first-match-wins policy in cirdan/incidents/routing.py (a registered service at qualifying severity defaults to reproduce_and_pr_only; everything else fails safe to triage_only), and become lifecycle-managed incidents in cirdan/incidents/. The responder (cirdan/incidents/responder.py) drives the repair: repair/workspace.py clones an isolated workspace (remote URL + auth from integrations/github.clone_context, whose push_url is always the canonical configured repo — pushes structurally cannot land anywhere else), the compose/k8s runners (repair/{compose_runner,k8s_runner}.py) reproduce the failure, agents/api_agent.py (in-process API providers) or agents/cli_agent.py (workspace-spawned host CLIs) edits the code, and verification (repair/{probe,testsuite,verify}.py) gates the PR (integrations/github.py). repair/delivery.py advances merge → deploy → prod-verify to resolved or manual_required; repair/{pr_checks,pr_comments,review_loop}.py watch CI and drive the @cirdan review loop; cirdan/readiness.py computes the checklist behind the setup UI banner and cirdan status --checks; the remaining adapters (docker, kubernetes, loki, prometheus, tempo) collect logs, state, and telemetry evidence only.
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 · 63 lines · 1,466 tokens per session scan A 796340d2902c
cirdan AGENTS.md is an instructions file published in the GitHub repository adanb13/cirdan (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,466 tokens to every session, about $0.0059 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-31.
Other instructions, from other repositories
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
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).