Skip to content

AGENTS.md

Latest commit

 

History

History
71 lines (46 loc) · 2.27 KB

AGENTS.md

File metadata and controls

71 lines (46 loc) · 2.27 KB
Raw

Agent Rules

These rules guide Codex when working inside this template repository or a copied Obsidian vault based on it.

Core Operating Rule

Plan first. Read narrowly. Execute with focused context.

Codex should not read the entire vault by default.

For most tasks, read only:

  1. Obsidian_Template/00_Index/operating_context_index.md
  2. the current Task Pack
  3. relevant pattern files
  4. a small number of necessary project files

Ask before expanding to large folders, raw archives, private directories, or a full vault scan.

Privacy Rules

  • Do not process private files unless the user explicitly asks and confirms they are safe to use.
  • Do not include private brand, client, or project names in public examples.
  • Do not include private messages, CRM data, customer records, account metrics, private screenshots, unpublished strategy, local file paths, API keys, access tokens, or private vault content.
  • Use mock examples only when creating public documentation.
  • Respect platform terms, copyright, creator rights, and privacy.
  • Do not download copyrighted media or private platform content without permission.

Automation Boundary

This is a manual workflow template.

Do not claim Codex is continuously monitoring Obsidian in the background.

Periodic organizing means the user runs a manual Codex prompt or configures their own future automation.

Do not create scraping tools, platform login automation, background watchers, content downloading scripts, or unauthorized platform automation.

Skill Safety

Do not install, enable, or update unaudited skills.

If a workflow references a third-party skill or repository, treat it as untrusted until the user asks for a security review and approves the result.

TaskPack Rule

Every TaskPack should define:

  • Purpose
  • When To Use
  • Default Read Files
  • Context Budget
  • Allowed Writes
  • Forbidden Actions
  • Required Checks
  • Output Format
  • Stop Rule
  • Error Correction Rule

Stop after the requested output is produced. Do not expand into adjacent work unless the user asks.

Error Correction Rule

When a mistake becomes reusable knowledge:

  1. record what went wrong
  2. record the correct behavior
  3. identify the root cause
  4. update the relevant rule, TaskPack, pattern, or memory file
  5. note how the next run should verify the fix