waybill AGENTS.md

Repository instructions for Waybill, a tool that packages unfinished agent work so it can move between coding agents.

In plain words
What is it for?
Use them when changing Waybill specifications, examples, adapters, skills, tests, commits, or privacy-related repository content.
Why use it?
They define where shared and agent-specific files belong and help prevent secrets, private data, generated files, and local artifacts from entering version control.

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

Made for: Codex, OpenCode.

Per session 630 This file is loaded in full into every session.
When invoked 630 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.00630 $0.00630
Opus 5 $0.00315 $0.00315
Sonnet 5 $0.00126 $0.00126
Haiku 4.5 $0.00063 $0.00063

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

Security

Grade A, and why

waybill 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 · 62 lines

How it starts

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

AGENTS.md

Waybill creates portable, local-first handoff bundles for moving unfinished agent work between coding agents.

  • Keep specs, examples, adapters, and generated text portable across agent CLIs.
  • Keep canonical shared resources only under skills/. Keep agent-specific wrappers only under adapters/, plus the repository-root Codex manifest and .agents/plugins/marketplace.json, in git. Standalone adapter bundles and agent-local installations are generated outputs.
  • Keep common dispatch and operation behavior under skills/. Limit adapter wrappers to platform metadata, exact agent identity, argument bridging, and platform-specific resource paths.
  • Do not commit local artifacts such as handoff bundles, package installs, caches, bytecode, archives, or generated reports.
  • Keep changes small, focused, and consistent with existing module boundaries.
  • Do not add dependencies unless clearly justified; prefer the Python standard library.

Privacy

  • Do not commit secrets, tokens, API keys, cookies, private user data, personal emails, local machine paths, real handoff bundles, archives, logs, screenshots, or private planning notes.
  • Keep examples and tests synthetic.
  • Do not weaken privacy, redaction, bundle validation, packing, or unpacking safeguards without focused tests.
  • Do not add release tags or release wording until an actual release is being prepared.

Checks

  • Run python3 scripts/validate-waybill.py after code, adapter, spec, example, or docs changes.
  • For Python changes, also run python3 -m py_compile cli/waybill waybill_core/*.py scripts/validate-waybill.py.
  • Add or update validation coverage for behavior changes, bug fixes, and privacy-sensitive paths. If a check cannot run locally, document why.
  • Use scripts/smoke-agents.sh --dry-run for smoke command generation. Only run real agent smoke tests when explicitly asked.
  • python3 scripts/validate-waybill.py builds standalone adapters in a disposable directory. Use scripts/build-adapters.py only when a local self-contained distribution is needed; do not commit its output.
  • There is no separate adapter synchronization step. Edit shared resources in skills/, edit only agent-specific wrappers in adapters/, and let the repository validator compare every generated distribution target.

Read the full file on GitHub · 62 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. 2d ago First seen · 62 lines · 630 tokens per session scan A ccae2df019cd

Subscribe to this mod's changes

waybill AGENTS.md is an instructions file published in the GitHub repository wardmos/waybill (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 630 tokens to every session, about $0.0032 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.