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 rules/compozy/gograph/compozy-shared-patternsgit clone --depth 1 https://github.com/compozy/gographWhat 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.00000 | $0.00580 |
| Opus 5 | $0.00000 | $0.00290 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
compozy-shared-patterns 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.
What it actually says
Compozy Shared Patterns
<configuration_overview type="shared_patterns"> Shared patterns include MCP integrations, reference syntax, and template expressions used across all Compozy configuration files. </configuration_overview>
MCP Integration Patterns
<mcp_patterns type="filesystem_mcp">
mcps:
- id: file_server
transport: stdio
command: npx
args:
- -y
- "@modelcontextprotocol/server-filesystem"
- "./"
proto: "2025-03-26"
start_timeout: 15s
</mcp_patterns>
<mcp_patterns type="http_mcp">
mcps:
- id: search-mcp
url: http://localhost:3000
transport: sse
env:
API_KEY: "{{ .env.SEARCH_API_KEY }}"
</mcp_patterns>
Reference Patterns
<reference_patterns type="local_references">
# Local references within the same file
$ref: local::schemas.#(id=="city_input")
$ref: local::tools.#(id=="weather_tool")
$ref: local::agents.#(id=="tourist_guide")
$ref: local::tasks.#(id=="save_results")
# Global references to project-level resources
$ref: global::models.#(provider=="groq")
# Resource references to external files
$ref: resource::agent::#(id=='file_reader')
</reference_patterns>
<reference_patterns type="use_patterns">
# Using tools
$use: tool(local::tools.#(id=="weather_tool"))
# Using agents
$use: agent(local::agents.#(id=="tourist_guide"))
$use: agent(resource::agent::#(id=='file_reader'))
</reference_patterns>
Template Expression Patterns
<template_patterns type="common_expressions">
# Workflow input access
"{{ .workflow.input.city }}"
# Task output access
"{{ .tasks.weather.output.temperature }}"
"{{ .tasks.activities.output | toJson }}"
# Collection item access
"{{ .item }}"
"{{ .index }}"
# Conditional expressions
'{{ .tasks.clothing.output.clothing | empty | ternary "no_clothes" "has_clothes" }}'
# Current timestamp
"{{ now }}"
# Array length
"{{ len .output }}"
</template_patterns>
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 · 99 lines · 0 tokens per session scan A 9dc04c3c024f
compozy-shared-patterns 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 580 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.