zaptrace: Instructions file for Codex

AGENTS.md

zaptrace AGENTS.md is an instructions file for Codex, OpenCode from oaslananka/zaptrace. It costs 2,225 tokens per session, scanned A, original, no licence file.

Repository instructions for the zaptrace project, stored in an AGENTS.md file. They describe which instructions apply, what the project is, where its files are, and the limits on product and evidence claims.

In plain words
What is it for?
They are for guiding agents working in the zaptrace codebase and deciding which repository instructions take precedence.
Why use it?
They give coding agents project-specific rules and context instead of leaving them to infer how the repository should be handled.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is oaslananka/zaptrace's own configuration. It tells Codex and OpenCode how to work on zaptrace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zaptrace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to oaslananka/zaptrace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/oaslananka/zaptrace/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/oaslananka/zaptrace

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for zaptrace AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/oaslananka/zaptrace/agents-md/github.svg)](https://agentmods.dev/instructions/oaslananka/zaptrace/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/oaslananka/zaptrace/agents-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/zaptrace/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for zaptrace AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/oaslananka/zaptrace/agents-md"><img src="https://agentmods.dev/badge/instructions/oaslananka/zaptrace/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,225 This file is loaded in full into every session.
When invoked 2,225 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown 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.1 $0.02225 $0.02225
Opus 5.5 $0.00890 $0.00890
Sonnet 5.5 $0.00445 $0.00445
Haiku 4.5 $0.00222 $0.00222

Measured 14d ago against content hash 7577b54895e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zaptrace 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 14d 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 · 243 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 14d ago First seen · 243 lines · 2,225 tokens per session scan A 7577b54895e7

Subscribe to this mod's changes

zaptrace AGENTS.md is an instructions file published in the GitHub repository oaslananka/zaptrace (0 stars, last pushed yesterday), with no licence file. It adds 2,225 tokens to every session, about $0.0089 per session on Opus 5.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-10-05.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens