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/openshift/lightspeed-agentic-operator/agents-mdgit clone --depth 1 https://github.com/openshift/lightspeed-agentic-operatorWhat 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.00966 | $0.00966 |
| Opus 5 | $0.00483 | $0.00483 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
lightspeed-agentic-operator 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Operator — project guide
Specs
All specifications live in .ai/spec/. Start with .ai/spec/README.md for project overview, reading order, and structure guide.
What lives where: agent.md (how agents should work), README.md (tests, make manifests, Makefile, cluster workflow, make api-lint, CEL / XValidation notes). This file is architecture and conventions for humans and agents editing the tree.
Module layout
go.mod— main module (github.com/openshift/lightspeed-agentic-operator): controller, CLI, etc.api/go.mod— API-only module so downstreams can depend on types without the operator. Rootgo.modusesreplace … => ./apifor local dev.
Key directories
| Path | Role |
|---|---|
api/v1alpha1/ |
CRD types, DerivePhase, constants |
controller/agenticrun/ |
AgenticRun reconciler, approval, sandbox wiring |
controller/agenticolsconfig/ |
AgenticOLSConfig reconciler |
controller/sandbox/ |
Sandbox pod management |
cli/ |
oc-agentic plugin |
config/crd/bases/ |
Generated CRD YAML (regen: README.md → make manifests) |
config/rbac/ |
SA, bindings, generated role.yaml |
config/manager/, config/default/ |
In-cluster Deployment kustomize |
examples/setup/ |
Day-0 YAML (agents, policies, runs) |
test/agent/ |
Mock agent HTTP server (POST /v1/agent/run), image Makefile, cmd/schemadump |
test/agent/sandboxtemplate/ |
Kustomize base SandboxTemplate for in-cluster mock |
test/e2e/ |
Build tag e2e: black-box tests against live cluster + running operator (make test-e2e) |
Run lifecycle phases
Derived from conditions via DerivePhase() — never stored on the spec:
Pending → Analyzing → Proposed → Executing → Verifying → Completed
→ Failed
→ Denied
→ Escalated
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.
- yesterday First seen · 82 lines · 966 tokens per session scan A fc2e07079768
lightspeed-agentic-operator AGENTS.md is an instructions file published in the GitHub repository openshift/lightspeed-agentic-operator (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 966 tokens to every session, about $0.0048 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
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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
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.