codetape AGENTS.md

Project instructions for Codetape, a tool that records meaningful code changes and keeps documentation aligned with the code. Its commands can trace changes, update documents, review drift, map architecture, and create commit messages.

In plain words
What is it for?
Use it to initialize Codetape, record and review changes, synchronize README or changelog files, map dependencies, inspect component history, and prepare commits.
Why use it?
It helps prevent documentation from becoming outdated or losing the reasons and effects behind code changes.

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/888wing/codetape/agents-md
Clone the repo
git clone --depth 1 https://github.com/888wing/codetape

Made for: Codex, OpenCode.

Per session 491 This file is loaded in full into every session.
When invoked 491 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.00491 $0.00491
Opus 5 $0.00246 $0.00246
Sonnet 5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured yesterday against content hash 1c9683bd263d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codetape 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 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.

AGENTS.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codetape — Agent Instructions

The flight recorder for AI coding — keeps your docs in sync with your code.

For AI Coding Agents

You are working in a project that uses Codetape for automatic documentation maintenance. Codetape records semantic traces of code changes and keeps documentation synchronized.

Available Commands

When .codetape/ exists in the project root, these commands are available:

Command Description
/trace Record a semantic trace of recent code changes — captures what changed, why, and what it affects
/trace-sync Sync documentation (README, CHANGELOG, CLAUDE.md) from recent traces
/trace-review Detect documentation drift — find docs that no longer match code reality
/trace-map Generate architecture documentation with dependency graphs
/trace-log [component] Query change history for a specific component
/trace-commit Generate a conventional commit message from the most recent trace
/trace-init Initialize Codetape tracking in this project

Data Directory

All Codetape data is stored in .codetape/:

.codetape/
├── config.json           # Project settings, sync targets, component roots
├── component-map.json    # Component registry with relationships
├── drift.json            # Current drift issues (transient)
├── traces/               # Session trace logs (markdown)
│   └── YYYY-MM-DD_HH-MM_{slug}.md
└── archive/              # Compressed monthly summaries

Behavior Guidelines

  1. After significant coding work (5+ files changed, new feature, major refactor): suggest running /trace
  2. Before modifying a component: check .codetape/component-map.json for dependencies and recent changes
  3. Never include API keys, tokens, or credentials in traces
  4. Write scope: only modify .codetape/, .claude/, and files listed in config.json sync_targets
  5. Quality standard: trace summaries must be independently understandable by a developer with no prior context

Read the full file on GitHub · 52 lines

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. yesterday First seen · 52 lines · 491 tokens per session scan A 1c9683bd263d

Subscribe to this mod's changes

codetape AGENTS.md is an instructions file published in the GitHub repository 888wing/codetape (0 stars, last pushed 5mo ago), licensed MIT. It adds 491 tokens to every session, about $0.0025 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-31.