AutoGineer
Generated banner for Open Knowledge Format for Crossplane v2
Generated logo for Open Knowledge Format for Crossplane v2

Open Knowledge Format for Crossplane v2

LLM wiki kit

First committed by jkroepke

Published in jkroepke/okf-crossplane-v2. Publisher page

37 GitHub stars

What it is

LLM-wiki in OKF (Open Knowledge Format) for Crossplane v2
— the description by jkroepke

AutoGineer overview, from the brain’s own files

The okf-crossplane-v2 repository provides a versioned, source-backed knowledge catalog designed to help AI agents and developers navigate the Crossplane v2 ecosystem. It aggregates information from Go API types, CRDs, package metadata, and documentation into a structured format. By utilizing the Open Knowledge Format (OKF), it enables agents to perform precise lookups on providers, composition functions, and API definitions. The project includes a dedicated MCP server that allows agents to query live repository data, such as CRD definitions, versioning, and examples, ensuring that the information retrieved is grounded in specific, versioned source code.

How it works

Memory model: LLM wiki

AutoGineer overview, from the brain’s own files

The system organizes technical knowledge into a catalog of Markdown files stored in the catalog folder. These files contain OKF metadata and provenance links. An MCP server, which can be self-hosted or used via a public endpoint, ingests this catalog into a DuckDB instance. Agents interact with this data through specific tools that resolve provider versions, search CRDs, and retrieve documentation or examples. The system relies on specialized researcher agents defined in the .agents folder to maintain and validate the knowledge base, ensuring that facts are linked to stable source code and documentation.

Folders
FolderRoleFiles
.codexagent-config25
.githubagent-config2
skillsagent-instructions1
.agentsfolder37
.codex-pluginfolder1
.okffolder2
.pifolder27
.pluginfolder1
catalogfolder120
mcpfolder12

Requirements

Apps: Docker

API keys (by name): GITHUB_TOKEN

Works with: Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Amp, Cline, JetBrains Junie, Devin (ex-Windsurf)

Set it up

  1. Download the brain as a ZIP and unzip it where you keep your notes or project: https://mp-staging.autogineer.com/agent-brains/jkroepke/okf-crossplane-v2/download

  2. Point Claude Code at .codex-plugin/plugin.json: it does not read that file on its own.

  3. cd okf-crossplane-v2 && claude

  4. AutoGineer scanned these files at commit df24ac2.

  5. Add crossplane-v2-okf to .mcp.json:

    {
  "mcpServers": {
    "crossplane-v2-okf": {
      "type": "http",
      "url": "https://crossplane.mcp.jkroepke.de/mcp"
    }
  }
}

  6. Or add it with the Claude Code CLI:

    claude mcp add --transport http crossplane-v2-okf https://crossplane.mcp.jkroepke.de/mcp

  7. Your data is sent to crossplane.mcp.jkroepke.de.

  8. First committed by jkroepke. Published in jkroepke/okf-crossplane-v2. Licence: Apache License 2.0.

Usage

AutoGineer overview, from the brain’s own files

  • Querying CRD definitions for specific Crossplane providers
  • Retrieving versioned examples for composition functions
  • Resolving stable provider versions and their associated documentation
  • Integrating Crossplane knowledge into AI agent workflows via MCP
“Find the latest version of the AWS provider and list its CRDs.”
The agent uses the get_versions and provider_crd_search tools to return the canonical repository name and a list of available CRDs for the specified provider.
“Show me the definition for the S3Bucket CRD in the latest AWS provider.”
The agent retrieves the YAML definition of the requested CRD using the provider_crd_get_definition tool, ensuring the output is token-efficient.

Documentation by jkroepke

Image: CI Image: GitHub license Image: GitHub Repo stars Image: BundleDex

Open Knowledge Format for Crossplane v2

This repository provides a structured knowledge catalog for the Crossplane v2 ecosystem using Open Knowledge Format v0.2.

The goal is to make Crossplane concepts, APIs, providers, composition functions, documentation, and practical examples easier to discover and understand. The catalog is designed for both humans and knowledge-aware tools.

Installation

WARNING
The public MCP server is a temporary early-access service for early adopters. Its availability is not guaranteed, and it may change or be removed without notice. It is intended to bridge the current tooling gap until the OKF ecosystem provides practical, end-user-friendly solutions that run locally. For reliable or production use, self-host the included container.

Install the companion skill and hosted OKF-aware MCP server together as a plugin for every detected supported agent:

npx plugins add jkroepke/okf-crossplane-v2

Pass --target codex to install only in Codex. Restart the selected agents after installation.

Alternatively, install the hosted OKF-aware MCP server globally:

npx add-mcp \
  https://crossplane.mcp.jkroepke.de/mcp \
  --name crossplane-v2-okf \
  --global

Then install the companion skill so the agent prefers this bundle over generic documentation providers for Crossplane v2 questions:

npx skills add jkroepke/okf-crossplane-v2 \
  --skill crossplane-v2-okf \
  --global

Both standalone installers detect supported agents and ask where the integration should be installed. Restart the selected agent after installation.

The public MCP health endpoint is available at https://crossplane.mcp.jkroepke.de/healthz.

Self-hosting the MCP server

The included container fetches this repository, ingests catalog/ into a DuckDB catalog, and serves the okf-mcp tools over Streamable HTTP.

docker compose up --build --detach

To authenticate the server's GitHub requests, export GITHUB_TOKEN before starting the container. The token is optional.

The local MCP endpoint is http://127.0.0.1:8000/mcp. Put it behind a TLS reverse proxy for crossplane.mcp.jkroepke.de.

The catalog is refreshed at container startup. If fetching or ingestion fails and a previous catalog exists in the volume, the server continues with that last successful catalog.

The MCP tools are read-only, but the public endpoint has no application-level authentication. Apply request limits and access controls at the reverse proxy when required.

Crossplane package tools

The server adds these tools backed by OSS GitHub repositories:

  • get_versions(name) resolves an OSS provider or function repository and returns its canonical repository name, versions.latest, a compact list of recent stable versions, and tag counts. Pass the returned provider name to the CRD tools.

  • provider_crd_search(provider_name, provider_version, crd_search_term) searches CRDs in one explicit provider package version. The search term supports case-insensitive shell-style wildcards.

  • provider_crd_get_definition(provider_name, provider_version, crd_name, path?) returns the complete CRD definition as token-efficient YAML. Use a dotted path such as .spec or .spec.versions[0] to return only a subtree.

  • provider_crd_get_examples(provider_name, provider_version, crd_name) returns GitHub repository paths for generated and handwritten examples. Without an API version, it selects the latest served CRD API version, for example examples-generated/namespaced/ec2/v1beta2/route.yaml.

  • provider_crd_get_terraform_docs(provider_name, provider_version, crd_name) returns the Terraform provider repository, version, and documentation path. It reads the Crossplane provider Makefile and the generated controller mapping instead of inferring the Terraform resource name.

crd_name accepts a Kind, group/Kind, group/version/Kind, or a YAML fragment containing apiVersion and kind.

Use an OSS GitHub repository name such as crossplane-contrib/provider-upjet-aws or crossplane-contrib/function-go-templating. A small set of historical package aliases is mapped to their known OSS source repositories; unmapped upbound/... names are rejected rather than guessed.

The CRD tools require an explicit provider version. The value latest is also supported and selects the highest stable semantic-version Git tag. Self-hosted deployments need outbound HTTPS access to GITHUB_API_URL and GITHUB_RAW_URL.

Successful remote fetches are cached in memory. Git tag listings use the configurable short FETCH_CACHE_TTL_SECONDS (default: 300 seconds); CRDs, definitions, examples, and Terraform metadata resolved at immutable Git tags are cached for 30 days. FETCH_CACHE_MAX_ENTRIES (default: 512) bounds memory use.

Why this repository exists

Crossplane knowledge is distributed across many repositories and kinds of sources:

  • Go API types and runtime implementations

  • CustomResourceDefinitions and OpenAPI schemas

  • package metadata

  • tests and executable examples

  • official Crossplane documentation

  • community implementations and real-world composition examples

Upjet-based providers add another layer. Their Crossplane managed resources are generated from Terraform provider resources, while the Terraform documentation often contains more details about the underlying cloud APIs and configuration fields.

This repository connects these sources in one versioned catalog without replacing the original documentation.

Knowledge structure

Knowledge is stored as small Markdown documents under catalog/. Each document represents an independently useful concept and includes OKF metadata, provenance in sources, keyed claim footnotes, and relationships to related concepts.

Repository validation pins okf-ingest 0.11.0, which adds OKF v0.2 core support, including generated.at freshness fallback and preservation of the new frontmatter families (upstream support commit).

If the task is to build a Crossplane v2 Composition, start with the Composition developer route. It routes agents through separate API/provider, pipeline/security, and testing/packaging concepts without pretending that provider-specific schemas or credentials are universal.

The catalog is intended to be:

  • Source-backed: important statements link to source code, schemas, tests, examples, or official documentation.

  • Version-aware: sources are tied to specific repository revisions.

  • Navigable: overview documents connect related concepts without requiring readers to know the source repository layout.

  • Incremental: providers, functions, services, documentation areas, and example repositories can be added in focused batches.

License

This project is licensed under the Apache License 2.0.

catalog/cli/control-plane-projects.md

type: Crossplane Development Guide title: Opt in to a Crossplane control plane project description: Choose the Beta CLI project wrapper explicitly before scaffolding, locally running, and packaging a new Composition-backed API. resource: https://docs.crossplane.io/cli/latest/get-started/get-started-with-control-plane-projects/ tags: [crossplane, cli, composition, project, authoring, packaging] generated: { by: "process:crossplane-okf-generation", at: "2026-10-16T20:40:00Z" } sources:

Agent opt-in gate

Before creating files for a new Composition or Composition-backed API, ask the requester one question unless they already selected a structure:

Would you like this wrapped as a Crossplane control plane project (CLI Beta), or should I create standalone Composition manifests?

Project mode is opt-in. Do not initialize a project, add crossplane-project.yaml, or reorganize existing manifests unless the requester chooses the project route. This decision rule is a catalog authoring policy, not a Crossplane requirement.

When the requester chooses standalone authoring, follow the standalone Composition manifest layout and standalone local rendering.

What the wrapper provides

The Crossplane CLI defines a project as a directory containing API definitions, Compositions, embedded Functions, examples, tests, operations, and a crossplane-project.yaml metadata file.[^project-definition-and-layout] The crossplane project command group is explicitly Beta; the locked v2.4 documentation warns that Beta features may change.[^project-command-beta-state]

Choose this route when the requester wants the CLI to manage an end-to-end authoring lifecycle:

  • scaffold the standard project directories and metadata;

  • generate an XRD and Composition;

  • record dependencies and generate an embedded Function;

  • discover and build embedded Functions during local rendering;

  • run the packages on a local KIND development control plane; and

  • build and push the resulting Configuration and embedded Function packages.

Documented route

  1. Initialize the selected directory with crossplane project init <name>. The name must be a DNS-1035 label; the command creates the project metadata and standard directories.[^project-init-contract]

  2. Define the XR API, then use the CLI generation commands where they fit the requested authoring approach. The guide covers XRD generation from an example XR or SimpleSchema, Composition generation, dependency addition, and embedded Function generation.[^project-generation-workflow] crossplane xrd generate writes <plural>/definition.yaml, or the --path target, inside the project's APIs directory and refuses to overwrite an existing file. From CLI v2.5.0, --replace overwrites it with the newly generated XRD; CLI v2.4.0 required a different path or deleting the file.[^xrd-generate-replace-flag][^xrd-generate-existing-file-handling][^xrd-generate-replace-tests][^xrd-generate-v2-4-existing-file-error] The write replaces the whole file, so hand edits to the generated XRD are lost (inferred from the full-file write). As a suggestion that follows from this inference, not documented practice, keep the example XR or SimpleSchema input as the source when regenerating. The xrd generate command is Beta.[^xrd-generate-existing-file-handling][^xrd-generate-v2-5-docs]

  3. From the project directory, render the example XR and Composition. Project mode discovers and builds the embedded Functions, so this invocation does not take the standalone Functions manifest argument.[^project-render-workflow]

  4. With a Docker-compatible runtime available, use crossplane project run for the local KIND control plane and registry. The command builds and pushes the embedded Function and Configuration packages, installs the Configuration, and selects the development cluster in the current kubectl context.[^project-run-workflow]

  5. Use crossplane project build and crossplane project push when the requester wants to publish the packages for installation on an existing Crossplane cluster.[^project-build-and-push-workflow]

Boundaries

  • Project commands are Beta; do not hide that lifecycle state when offering the option.[^project-command-beta-state]

  • crossplane-project.yaml uses the CLI's dev.crossplane.io/v1alpha1 Project metadata API, so that API is Alpha even though the surrounding command workflow is Beta.[^project-metadata-api-version] The metadata describes a buildable Configuration and its dependencies, Functions, paths, architectures, and schema generation; it is not a Kubernetes resource and has no status.[^project-api-boundary]

  • Local project execution requires a Docker-compatible runtime because the guide builds Functions and creates a KIND cluster.[^project-runtime-prerequisites]

  • Generating an XRD from an example XR cannot express field types, defaults, validation rules, or descriptions. Use the guide's SimpleSchema route or author the XRD schema directly when those controls are required.[^xrd-generation-boundary]

  • From CLI v2.5.0, a crossplane xrd generate --from simpleschema input can declare reusable types in a top-level customTypes map. Spec and status fields reference them by name, and the generated XRD expands them inline as object schemas.[^simpleschema-custom-types-input][^simpleschema-custom-types-conversion][^simpleschema-custom-types-test] The example-XR route rejects the key because it allows only apiVersion, kind, metadata, spec, status, and additionalPrinterColumns.[^example-xr-top-level-keys] The SimpleSchema parser comes from kro v0.9.2, whose documentation names the same section types and describes types that reference other types. Use customTypes with the Crossplane CLI. The CLI test ignores Required when comparing schemas, so it does not check how required propagates inside a custom type.[^simpleschema-custom-types-test] The xrd command group is Beta.[^kro-simpleschema-custom-types][^xrd-command-group-beta]

  • Project wrapping does not replace the Composition design and verification gates. Continue through the Composition developer route, including provider schema selection, security review, render assertions, live smoke tests, and package validation.

[^project-command-beta-state]: Crossplane project command Beta state [^project-definition-and-layout]: Control plane project definition and layout [^project-init-contract]: Project initialization contract [^project-generation-workflow]: API, Composition, dependency, and Function generation workflow [^project-render-workflow]: Project-mode Composition rendering [^project-run-workflow]: Local project development control plane [^project-runtime-prerequisites]: Local project runtime prerequisites [^project-build-and-push-workflow]: Project build and push workflow [^xrd-generation-boundary]: Example-XR XRD generation boundary [^project-api-boundary]: Project metadata API boundary [^project-metadata-api-version]: Project metadata API version [^xrd-generate-replace-flag]: CLI v2.5.0 xrd generate --replace flag [^xrd-generate-existing-file-handling]: CLI v2.5.0 output path and existing-file handling [^xrd-generate-replace-tests]: CLI v2.5.0 existing-file and replace tests [^xrd-generate-v2-5-docs]: CLI v2.5 xrd generate Beta label and flags [^xrd-generate-v2-4-existing-file-error]: CLI v2.4.0 existing-file error without --replace [^simpleschema-custom-types-input]: CLI v2.5.0 SimpleSchema input with customTypes [^simpleschema-custom-types-conversion]: CLI v2.5.0 customTypes passed to spec and status conversion [^simpleschema-custom-types-test]: CLI v2.5.0 customTypes expansion test [^example-xr-top-level-keys]: CLI v2.5.0 example-XR allowed top-level keys [^xrd-command-group-beta]: CLI v2.5.0 xrd command group maturity label [^kro-simpleschema-custom-types]: kro v0.9.2 SimpleSchema custom types

242 files

Advantages

  • Provides version-aware knowledge by linking facts to specific repository revisions. evidence: README.md
  • Connects distributed sources like Go APIs, CRDs, and documentation into a single navigable catalog. evidence: README.md

Limitations

  • The public MCP server is provided as an early-access service and is not intended for production use without self-hosting. evidence: README.md
  • Requires explicit provider versions for CRD tools, as it does not guess or infer versions automatically. evidence: README.md

Security

Risk level: Low risk

This brain runs

Agent instructions that run or fetch something (26)

  • .agents/agents/okf-function-go-templating-researcher/AGENT.md: Write for Crossplane users who want to install and use `function-go-templating` in Compositions.
  • .agents/agents/okf-reviewer/AGENT.md: `mise run lint` succeeds after the final fixes and before the root or parent agent creates a commit.
  • .agents/agents/okf-reviewer/AGENT.md: Run `mise run lint` as the final validation command.
  • .agents/skills/okf-open-knowledge-format/SKILL.md: If the user agrees to install:
  • .agents/skills/okf-open-knowledge-format/SKILL.md: uv tool install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: pip install okflint
  • .agents/skills/okf-open-knowledge-format/SKILL.md: kcmd push --dry-run
  • .agents/skills/okf-updates/SKILL.md: Run this workflow only after the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • .agents/skills/okf-updates/SKILL.md: Run at most three direct researchers at once.
  • .agents/skills/okf-updates/SKILL.md: A requester reply that selects one or more candidate IDs from this explicitly invoked workflow is explicit permission to run the normal OKF update logic for those candidates.
  • .agents/skills/okf-updates/SKILL.md: Run deterministic validation, `okf-reviewer`, and `mise run lint`.
  • .agents/skills/okf/SKILL.md: Run this workflow only after the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`.
  • .agents/skills/okf/SKILL.md: After all review fixes, run `mise run lint`.
  • .agents/skills/okf/SKILL.md: Commit every intended file only after reviewer approval and a successful lint run.
  • .agents/skills/okf/SKILL.md: Run the Core docs and Core code researchers together when a concept needs both user-facing guidance and exact served API shape.
  • .agents/skills/okf/SKILL.md: Run independent read-heavy research in parallel, with at most three direct agents.
  • .agents/skills/okf/SKILL.md: After all fixes, run `mise run lint` and fix every reported issue.
  • .agents/skills/okf/SKILL.md: The reviewer may return `APPROVED` only after the final lint run succeeds.
  • .agents/skills/okf/SKILL.md: Non-thinking coding models such as Qwen3-Coder-Next can run every project agent without incompatible reasoning controls.
  • .agents/skills/okf/SKILL.md: deterministic validation and `mise run lint` results
  • AGENTS.md: Run the normal workflow only when the user explicitly invokes `$okf`, `/skill:okf`, or `/okf`, or selects a feature candidate returned by an explicitly invoked `$okf-updates`, `/skill:okf-updates`, or `/okf-updates` workflow.
  • AGENTS.md: Run update discovery only when the user explicitly invokes `$okf-updates`, `/skill:okf-updates`, or `/okf-updates`.
  • AGENTS.md: Run deterministic validation and the `okf-reviewer` before committing the changes.
  • AGENTS.md: After the final review fixes, run `mise run lint` before creating any commit.
  • AGENTS.md: After reviewer approval and a successful lint run, commit every intended change.
  • AGENTS.md: Create commits with a Developer Certificate of Origin sign-off by default by using `git commit --signoff` (or `git commit -s`).

MCP servers (1)

  • .mcp.json (crossplane-v2-okf): https://crossplane.mcp.jkroepke.de/mcp · uses the network
  • Low risk: network-instructions (.agents/skills/okf-open-knowledge-format/SKILL.md:214)

Attribution and licence

First committed by
GitHub avatar of jkroepkejkroepke
Publisher
Jan-Otto Kröpke (Community)
Source
jkroepke/okf-crossplane-v2 · commit df24ac2
Licence
Apache License 2.0 (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
jkroepke

AutoGineer is not affiliated with or endorsed by jkroepke.

Download

The ZIP holds the files AutoGineer serves, with ATTRIBUTION.md and the licence. Download okf-crossplane-v2.zip