Traceplane AGENTS.md

A set of repository rules for Traceplane, an application that records how coding agents work and connects their memories, actions, traces, and generated files. It describes the required implementation order and boundaries between data and control features.

In plain words
What is it for?
Use it when implementing Traceplane schemas, database migrations, APIs, permissions, audit logs, tests, MCP support, command-line tools, or a small demo.
Why use it?
It gives an agent clear constraints for building the core data model first, keeping history traceable, and recording security-related actions.

Instructions file for CodexOpenCode

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 instructions/jaxxchen003/traceplane/agents-md
Clone the repo
git clone --depth 1 https://github.com/jaxxchen003/Traceplane

Made for: Codex, OpenCode.

Per session 624 This file is loaded in full into every session.
When invoked 624 The same file — it is already loaded in full.
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.00624 $0.00624
Opus 5 $0.00312 $0.00312
Sonnet 5 $0.00125 $0.00125
Haiku 4.5 $0.00062 $0.00062

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

Security

Grade A, and why

Traceplane AGENTS.md 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.

AGENTS.md · 79 lines

What it actually says

AGENTS.md

本文件定义本仓库内 Agent 的实现规则。目标不是做大而全平台,而是尽快证明 Enterprise Agent Work Graph 的最小闭环。

1. 实现顺序

  1. 先实现 schema
  2. 再实现 migrations / fixtures / tests
  3. 再实现 episode / memory / trace / artifact API
  4. 再补 permission / audit
  5. 最后接 MCP / CLI 和最小 demo

2. 绝对约束

  • 不先做重 UI
  • 不做与 MVP 无关的抽象层
  • 所有核心对象都必须可回链到 episode
  • 所有写接口都必须产生日志或审计事件
  • 所有输出都必须能回链到来源 trace
  • 历史记录默认不可静默覆盖

3. 保底字段

以下字段原则上应成为核心对象的通用字段:

  • workspace_id
  • project_id
  • episode_id
  • agent_id
  • sensitivity
  • policy_version
  • created_at
  • created_by

4. 模块边界

Data Plane

  • episodes
  • memory_items
  • trace_events
  • artifacts
  • node_edges

Control Plane

  • policies
  • access_grants
  • audit_events

5. API 约束

  • create_episode 必须记录触发者和生效 policy
  • write_memory 必须带来源和敏感级别
  • append_trace 必须支持引用已有 memory / artifact / policy
  • create_artifact 必须声明来源 episode 和生成 agent
  • grant_access 必须写入审计
  • read_audit_events 必须受严格权限控制

6. 审计规则

  • 读取敏感数据要审计
  • 写入核心对象要审计
  • 删除、导出、分享必须审计
  • 权限拒绝和策略命中必须审计

7. 测试优先级

  • Episode 主链路能否跑通
  • Artifact 是否可追溯到 trace 和 memory
  • 权限拒绝是否留下审计证据
  • 历史 policy version 是否被正确固化

8. 默认技术假设

  • Postgres 作为主库
  • Object Storage 承载 artifact 文件
  • Vector 索引异步构建
  • Queue 处理蒸馏、索引、归档和重试

9. 交付标准

任何新功能提交前,至少要回答:

  • 它挂在哪个 episode 主线上?
  • 它会产生哪些节点和边?
  • 它是否会影响权限或审计?
  • 管理者是否能复盘这次行为?
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 · 79 lines · 624 tokens per session scan A ddef0da0c70e

Subscribe to this mod's changes

Traceplane AGENTS.md is an instructions file published in the GitHub repository jaxxchen003/Traceplane (36 stars, last pushed 3mo ago), licensed MIT. It adds 624 tokens to every session, about $0.0031 per session on Opus 5. 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-30.

Related

Other instructions, from other repositories