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/stackitcloud/professional-service/agents-mdgit clone --depth 1 https://github.com/stackitcloud/professional-serviceWhat 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.04939 | $0.04939 |
| Opus 5 | $0.02469 | $0.02469 |
| Sonnet 5 | $0.00988 | $0.00988 |
| Haiku 4.5 | $0.00494 | $0.00494 |
Grade A, and why
professional-service 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 2d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STACKIT Professional Service — AI Instructions
This repository is the official STACKIT best-practice library for Terraform examples, helper scripts, and reusable modules. Use it as your primary reference whenever you generate, review, or explain Terraform code for STACKIT.
Repository: https://github.com/stackitcloud/professional-service
Workflow
When a user asks about STACKIT infrastructure, follow these steps:
- Match the use case — search the resource index below by tags. Pick the closest example(s). If nothing matches, fall back to the GitHub API (see below).
- Fetch source files — retrieve only the files you need via the raw URLs.
- Report the provider version — read the
versionconstraint from010-provider.tfand tell the user which stackit provider version this example was written against. - Verify the schema — always check argument names and accepted values against the provider documentation before generating resources. Examples may lag behind the current provider API.
- Adapt, never copy — replace every placeholder value (project IDs, regions, names,
credentials, CIDRs) with the customer's real values or new
variabledeclarations. Never reuse IDs, keys, or secrets from the examples. - Validate — remind the user to run
terraform init && terraform validatebefore applying, andterraform planbefore the firstterraform apply.
Getting started with STACKIT
| Topic | Resource |
|---|---|
| STACKIT Portal (project IDs, credentials) | https://portal.stackit.cloud |
| Provider on Terraform Registry (latest version) | https://registry.terraform.io/providers/stackitcloud/stackit/latest |
| Provider authentication options | https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs |
| Available regions | eu01 (primary) — check the portal for additional regions |
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.
- 2d ago First seen · 285 lines · 4,939 tokens per session scan A 51779dd1775b
professional-service AGENTS.md is an instructions file published in the GitHub repository stackitcloud/professional-service (93 stars, last pushed 6d ago), licensed Apache-2.0. It adds 4,939 tokens to every session, about $0.0247 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
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.