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/xrf9268-hue/aiops-platform/agents-mdgit clone --depth 1 https://github.com/xrf9268-hue/aiops-platformWrote 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/xrf9268-hue/aiops-platform/agents-md)<a href="https://agentmods.dev/instructions/xrf9268-hue/aiops-platform/agents-md"><img src="https://agentmods.dev/badge/instructions/xrf9268-hue/aiops-platform/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.08759 | $0.08759 |
| Opus 5 | $0.04380 | $0.04380 |
| Sonnet 5 | $0.01752 | $0.01752 |
| Haiku 4.5 | $0.00876 | $0.00876 |
Grade A, and why
aiops-platform 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 — 538 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project guide for AI coding agents (Codex CLI, Claude Code, etc.) working in this repo.
This file is the single source of truth for all engineering rules. Other
coding agents read it via thin bridge files: CLAUDE.md imports it with
@AGENTS.md for Claude Code. Do not duplicate content in the bridge files —
update only this file.
Each rule is kept to a scannable imperative; the provenance (the observed
failure that earned it, per harness principle 2)
lives in docs/engineering-rules-rationale.md,
linked per section (and per rule where useful) as (provenance). When you add or
change a rule here, update its rationale entry there too.
Index
- What this project is — scope, the scheduler/runner boundary, transitional reverts
- SPEC alignment is a hard requirement — the authoritative sources
- Harness engineering principles — how to evaluate components (1–8)
- Cross-cutting checklist — Elixir-port failure classes + rules for agents
- Layout · Build, test, lint
- Clean code — per-PR rules (1–11)
- Conventions — gofmt, timeouts, goroutines, secrets, gates
- WORKFLOW.md discovery · Where to read next · Safety posture
DEVIATIONS.md— tracked SPEC deviations ·docs/engineering-rules-rationale.md— rule provenance
What this project is
aiops-platform is a Go-based, self-hostable AI coding orchestrator that
implements the OpenAI Symphony SPEC.
The orchestrator polls a tracker (Linear, Gitea, or GitHub), prepares a
deterministic per-issue workspace, runs a coding agent in that workspace, and
watches the agent's lifecycle. Per SPEC §1, the agent is what writes
tickets, opens PRs, and pushes branches — through tooling available in its
workflow/runtime: the orchestrator-advertised dynamic tools linear_graphql
(Linear) and gitea_issue_labels (Gitea), or gh/local workflow tooling for
GitHub (which has no orchestrator-advertised tool). The orchestrator is the
scheduler/runner and tracker reader, not a tracker writer.
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 · 538 lines · 8,759 tokens per session scan A f64f830190d0
aiops-platform AGENTS.md is an instructions file published in the GitHub repository xrf9268-hue/aiops-platform (2 stars, last pushed today), licensed Apache-2.0. It adds 8,759 tokens to every session, about $0.0438 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).
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.
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).