compozy-project-config

A reference for configuring Compozy projects in compozy.yaml, including project details, workflows, models, and runtime permissions.

In plain words
What is it for?
Use it to define project metadata, connect workflow files, configure AI model providers, and set permissions such as reading files or accessing the network.
Why use it?
It gives you example layouts for settings that can otherwise be difficult to organize correctly.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/compozy/gograph/compozy-project-config
Clone the repo
git clone --depth 1 https://github.com/compozy/gograph

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00599
Opus 5 $0.00000 $0.00300
Sonnet 5 $0.00000 $0.00120
Haiku 4.5 $0.00000 $0.00060

Measured 2d ago against content hash eeeddde24f5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

compozy-project-config 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.

.cursor/rules/compozy-project-config.mdc · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Compozy Project Configuration Examples

<configuration_overview type="project_config"> Project configuration defines the top-level settings for Compozy projects including models, workflows, autoload settings, and runtime permissions. </configuration_overview>

Basic Project Configuration

<project_config_pattern type="basic">

name: project-name
version: 0.1.0
description: Project description

workflows:
  - source: ./workflow.yaml

runtime:
  permissions:
    - --allow-read
    - --allow-net
    - --allow-env

</project_config_pattern>

Project with Model Configuration

<project_config_pattern type="with_models">

name: weather-agent
version: "0.1.0"
description: A multi-agent weather advisory system

author:
  name: Pedro Nauck
  url: https://github.com/compozy

workflows:
  - source: ./workflow.yaml

models:
  - provider: groq
    model: llama-3.3-70b-versatile
    api_key: "{{ .env.GROQ_API_KEY }}"
  - provider: ollama
    model: llama4:16x17b
    api_url: "http://localhost:11434"

runtime:
  permissions:
    - --allow-read
    - --allow-net
    - --allow-env
    - --allow-sys
    - --allow-write

</project_config_pattern>

Project with AutoLoad Configuration

<project_config_pattern type="with_autoload">

name: project-name
version: 0.1.0

workflows:
  - source: ./workflow.yaml

# AutoLoad configuration for discovering agents and tools
autoload:
  enabled: true
  strict: true
  include:
    - "agents/*.yaml"
    - "tools/*.yaml"
  exclude:
    - "**/*~"
    - "**/*.bak"
    - "**/*.tmp"

runtime:
  permissions:
    - --allow-read
    - --allow-net
    - --allow-env

</project_config_pattern>

Environment Variable Patterns

<environment_patterns type="api_keys">

# Environment variable references
api_key: "{{ .env.GROQ_API_KEY }}"
api_key: "{{ .env.OPENAI_API_KEY }}"
database_url: "{{ .env.DATABASE_URL }}"

# MCP environment variables
mcps:
  - id: external_service
    url: "{{ .env.MCP_SERVICE_URL }}"
    env:
      API_KEY: "{{ .env.EXTERNAL_API_KEY }}"
      TIMEOUT: "{{ .env.REQUEST_TIMEOUT | default \"30s\" }}"

</environment_patterns>

Read the full file on GitHub · 114 lines

Changes

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.

  1. 2d ago First seen · 114 lines · 0 tokens per session scan A eeeddde24f5e

Subscribe to this mod's changes

compozy-project-config is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 599 tokens. 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.