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.
git clone --depth 1 https://github.com/compozy/gographWrote 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/rules/compozy/gograph/compozy-examples)<a href="https://agentmods.dev/rules/compozy/gograph/compozy-examples"><img src="https://agentmods.dev/badge/rules/compozy/gograph/compozy-examples/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/compozy/gograph/compozy-examples"><img src="https://agentmods.dev/badge/rules/compozy/gograph/compozy-examples.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00513 |
| Opus 5.5 | $0.00000 | $0.00205 |
| Sonnet 5.5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
compozy-examples 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 1mo 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.
What it actually says
Compozy Configuration Examples Index
<configuration_overview type="yaml_patterns"> Compozy uses YAML configuration files to define projects, workflows, agents, tools, and runtime settings. This index references focused documentation for each configuration type. </configuration_overview>
Configuration File Types
Project Configuration (compozy.yaml)
See compozy-project-config.mdc for:
- Basic project configuration
- Model configuration patterns
- AutoLoad configuration
- Runtime permissions
- Environment variable patterns
Workflow and Task Configuration
See compozy-task-patterns.mdc for:
- All task type patterns (basic, composite, parallel, collection, router, signal, aggregate)
- Workflow configuration structure
- Tool configuration
- Execution strategies
- Trigger patterns
- Deno configuration
Agent Configuration
See compozy-agent-config.mdc for:
- Basic agent configuration
- Agent instructions and actions
- Agent with MCP integration
- Tool integration patterns
Shared Patterns
See compozy-shared-patterns.mdc for:
- MCP integration patterns (filesystem, HTTP)
- Reference patterns (local, global, resource)
- Template expression patterns
- Use patterns for tools and agents
Quick Reference
# Basic project structure
name: project-name
version: 0.1.0
workflows:
- source: ./workflow.yaml
# Basic task structure
- id: task_name
type: basic
$use: tool(local::tools.#(id=="tool_name"))
with:
param: "{{ .workflow.input.value }}"
# Basic agent structure
resource: agent
id: agent_name
config:
provider: groq
model: llama-3.3-70b-versatile
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.
- 1mo ago First seen · 74 lines · 0 tokens per session scan A 952c58562ff2
compozy-examples 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 513 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.