CtrlK
BlogDocsLog inGet started
Tessl Logo

rules

Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/omo/components/rules/skills/rules/SKILL.md
SKILL.md
Quality
Evals
Security

Codex Rules

Codex Rules is automatic once the plugin is enabled. It injects:

  • static project instructions on SessionStart and UserPromptSubmit
  • matching file-specific rules after Codex apply_patch by default

Dynamic PostToolUse output is injected as additional context and is deduplicated per plugin data session. Codex Rules does not rewrite tool output.

Supported project sources:

  • CONTEXT.md
  • .omo/rules/**/*.md
  • .claude/rules/**/*.md
  • .cursor/rules/**/*.md
  • .github/instructions/**/*.md
  • .github/copilot-instructions.md

Supported environment knobs:

  • CODEX_RULES_DISABLED=1
  • CODEX_RULES_MODE=both|static|dynamic|off
  • CODEX_RULES_MAX_RULE_CHARS=<number>
  • CODEX_RULES_MAX_RESULT_CHARS=<number>
  • CODEX_RULES_ENABLED_SOURCES=CONTEXT.md,.omo/rules

The legacy PI_RULES_* variables are accepted as fallbacks for users migrating from pi-rules.

Repository
code-yeongyu/lazycodex
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.