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/gridctl/gridctl/agents-mdgit clone --depth 1 https://github.com/gridctl/gridctlWhat 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.02750 | $0.02750 |
| Opus 5 | $0.01375 | $0.01375 |
| Sonnet 5 | $0.00550 | $0.00550 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
gridctl 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents working in this repository. Follows the agents.md open specification: a single, predictable entry point for agent-relevant context. Human-facing onboarding lives in README.md and CONTRIBUTING.md; agent-specific tooling files (CLAUDE.md, etc.) re-export this file rather than duplicating it.
What gridctl is
Gridctl is an MCP (Model Context Protocol) gateway with a built-in skills and agents registry. A user declares a stack of MCP servers (containerized stdio, SSE/HTTP, OpenAPI-backed, local processes, SaaS proxies) in stack.yaml, runs gridctl apply, and gridctl orchestrates the containers, fans tool calls to the right server, and surfaces every active SKILL.md to upstream clients as an MCP prompt. A projection engine (pkg/project, one lockfile at ~/.gridctl/project.lock.yaml) also places skills, agents, global-context rules, and gateway wiring onto disk for file-reading clients, and packs (gridctl-pack.yaml) import all of it from one git repo. The same process embeds a React web UI on :8180. Inspired by Containerlab.
Build and run
Task (https://taskfile.dev) is the entry point for everything; tasks live in Taskfile.yml. Run task --list for the full catalog and task --summary <name> for per-task notes. Install with brew install go-task/tap/go-task (or npm install -g @go-task/cli, or go install github.com/go-task/task/v3/cmd/task@latest). A transitional Makefile shim forwards the old make <target> names. Common tasks:
| Task | Notes |
|---|---|
task build |
Builds the web frontend (web/dist → cmd/gridctl/web/dist), then builds the Go binary with -tags embed_web so the UI is embedded. Produces ./gridctl in the repo root. |
task build:go |
Backend only. Skips the embed tag if cmd/gridctl/web/dist is absent (UI 404s in that case). |
task build:web |
Frontend only (cd web && npm run build). |
task dev |
Runs the Vite dev server (web/) against a separately-running backend. |
task test |
go test -race ./... (unit tests only, same race detector CI runs). |
task test:integration |
go test -tags=integration -race -timeout 5m ./tests/integration/.... Requires Docker (or Podman). These tests hit real container runtimes per Article IV of CONSTITUTION.md; mocks are disallowed in tests/integration/. |
task test:frontend |
cd web && npm test (Vitest). |
task lint |
golangci-lint run plus npm run lint in web/ (both CI-gated). |
task generate |
Regenerates go.uber.org/mock mocks under pkg/mcp/ and pkg/runtime/. Required after touching the interfaces they're generated from. |
task mock:servers |
Builds and runs the example mock MCP servers in examples/_mock-servers/ (HTTP on PORT, SSE on PORT+1; PORT=9001 default). Pair with task mock:clean. |
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 · 126 lines · 2,750 tokens per session scan A 75ed75e2f7fb
gridctl AGENTS.md is an instructions file published in the GitHub repository gridctl/gridctl (45 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,750 tokens to every session, about $0.0137 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-30.
Other instructions, from other repositories
ollama AGENTS.md
Instructions for ollama/ollama, covering agents.md and building.
go-micro CLAUDE.md
Instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
ollama CLAUDE.md
Instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
sq AGENTS.md
Instructions for neilotoole/sq, covering agents.md, about sq, key documents, common commands and conventions.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.