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/redhatinsights/nxtcm-components/agents-mdgit clone --depth 1 https://github.com/RedHatInsights/nxtcm-componentsWrote 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/redhatinsights/nxtcm-components/agents-md)<a href="https://agentmods.dev/instructions/redhatinsights/nxtcm-components/agents-md"><img src="https://agentmods.dev/badge/instructions/redhatinsights/nxtcm-components/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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
nxtcm-components 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 3d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
repo context for ai coding agents. this file is intentionally thin: routing + repo-wide constraints only.
what is this repo?
npm workspaces monorepo of shared react component libraries for Red Hat ACM (Advanced Cluster Management) and OCM (OpenShift Cluster Manager) console UIs.
workspace packages:
@redhat-cloud-services/nxtcm-dashboard(packages/nxtcm-dashboard) — workspace package@redhat-cloud-services/nxtcm-rosa-hcp-wizard(packages/nxtcm-rosa-hcp-wizard) — workspace package
hard constraints
- never make http calls from components, consuming apps own backend communication.
- before writing or modifying any component file, you MUST read the task-type doc from
docs/agent-rules/that matches the work (e.g.,ui-component.mdfor component code). Do not skip this step. Refer to the task routing section for a list of docs. - run verification commands before finishing changes.
- use package-specific overlays (
packages/*/AGENTS.md) for domain rules, do not put package detail in this root file.
layering model
- this root file = workspace routing + repo-wide rules.
docs/agent-rules/*.md= task-type guidance (new component, storybook, ct, workflows, typescript).packages/nxtcm-dashboard/AGENTS.md= dashboard-only domain behavior.packages/nxtcm-rosa-hcp-wizard/AGENTS.md= wizard-only domain behavior.
project map
packages/
nxtcm-dashboard/
nxtcm-rosa-hcp-wizard/
docs/agent-rules/ # task-type rulebooks
.github/workflows/ # ci workflows
where to add code
- dashboard widget work:
packages/nxtcm-dashboard/src/ - rosa hcp wizard work:
packages/nxtcm-rosa-hcp-wizard/src/
path aliases
@redhat-cloud-services/nxtcm-dashboard→packages/nxtcm-dashboard/src@redhat-cloud-services/nxtcm-rosa-hcp-wizard→packages/nxtcm-rosa-hcp-wizard/src@/→ resolves differently per tool (vite/ts: repo root, storybook/playwright/jest:src/)
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.
- 3d ago First seen · 70 lines · 691 tokens per session scan A c93c4ce5a30c
nxtcm-components AGENTS.md is an instructions file published in the GitHub repository RedHatInsights/nxtcm-components (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 691 tokens to every session, about $0.0035 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
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.
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.
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).
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.