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/platform-frontend-ai-toolkit/agents-mdgit clone --depth 1 https://github.com/RedHatInsights/platform-frontend-ai-toolkitWrote 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/platform-frontend-ai-toolkit/agents-md)<a href="https://agentmods.dev/instructions/redhatinsights/platform-frontend-ai-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/redhatinsights/platform-frontend-ai-toolkit/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.02371 | $0.02371 |
| Opus 5 | $0.01185 | $0.01185 |
| Sonnet 5 | $0.00474 | $0.00474 |
| Haiku 4.5 | $0.00237 | $0.00237 |
Grade A, and why
platform-frontend-ai-toolkit 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Frontend AI Toolkit
Project Overview
An Nx monorepo serving as a centralized hub for AI-assisted development tools used by the HCC (Hybrid Cloud Console) frontend and infrastructure teams. The repository provides:
- Claude Code plugin — custom sub-agents distributed via a custom marketplace
- Cursor editor rules — auto-generated from Claude agents via conversion scripts
- MCP servers — Model Context Protocol servers published to npm as standalone packages
Tech Stack
| Technology | Purpose |
|---|---|
| TypeScript ~5.9 | Primary language for MCP servers |
| Nx 22.1 | Monorepo build orchestration, task caching, release management |
| Node.js 20 | Runtime for MCP servers and scripts |
| Jest 30 | Unit testing for MCP server packages |
| MCP SDK ^1.22 | Model Context Protocol server framework |
| Zod ^3.25 | Schema validation (required by MCP SDK for tool definitions) |
| Husky | Pre-push hooks (cursor-sync check) |
| Prettier | Code formatting |
Project Structure
platform-frontend-ai-toolkit/
├── .claude-plugin/
│ └── marketplace.json # Marketplace config (lists all plugins)
├── .github/workflows/
│ ├── ci.yml # Build, lint, test
│ └── release.yml # NX Release → versions + publishes packages/plugins
├── .mcp.json # Local MCP config (nx-mcp for dev)
├── plugins/
│ ├── frontend/ # Frontend development plugin
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json # Plugin manifest
│ │ ├── agents/ # 14 frontend agents
│ │ ├── package.json # For NX versioning (private)
│ │ └── project.json # NX project config
│ ├── infrastructure/ # Infrastructure & DevOps plugin
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json
│ │ ├── agents/ # 17 infrastructure agents
│ │ ├── skills/ # Utility skills (db-upgrader)
│ │ ├── package.json
│ │ └── project.json
│ └── management/ # Project management plugin
│ ├── .claude-plugin/
│ │ └── plugin.json
│ ├── agents/ # 3 management agents
│ ├── package.json
│ └── project.json
├── packages/
│ ├── hcc-pf-mcp/ # @redhat-cloud-services/hcc-pf-mcp
│ ├── hcc-feo-mcp/ # @redhat-cloud-services/hcc-feo-mcp
│ └── hcc-kessel-mcp/ # @redhat-cloud-services/hcc-kessel-mcp
├── scripts/
│ └── sync-plugin-versions.js # Syncs package.json version → plugin.json
├── docs/ # Documentation
├── nx.json # NX workspace config
└── package.json # Root workspace package
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 · 193 lines · 2,371 tokens per session scan A 21465255ae52
platform-frontend-ai-toolkit AGENTS.md is an instructions file published in the GitHub repository RedHatInsights/platform-frontend-ai-toolkit (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 2,371 tokens to every session, about $0.0119 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.
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.
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.
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).