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.
npx agentmods add instructions/ttcmarine/expedition-python/agents-mdgit clone --depth 1 https://github.com/TTCMarine/Expedition-PythonWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01402 | $0.01402 |
| Opus 5 | $0.00701 | $0.00701 |
| Sonnet 5 | $0.00280 | $0.00280 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
Expedition-Python 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent and contributor guide
This file helps AI assistants (Cursor, etc.) and contributors work effectively on Expedition-Python.
What this project is
A Python ctypes wrapper around Expedition’s ExpDLL.dll for sailing navigation integration on Windows.
| Area | Location |
|---|---|
| DLL wrapper | Expedition/dll_wrapper.py |
| Channel / system enums | Expedition/enums.py |
| Package version | Expedition/version.py (dynamic in pyproject.toml) |
| Tests | tests/test_expedition.py |
| User docs (Sphinx) | docs/, built via readthedocs.yaml |
Runtime: Windows only for real DLL use. CI runs on Windows only; integration tests skip when ExpDLL.dll is unavailable.
Reference headers (local dev, not in git)
Expedition’s C headers are proprietary. Sync them locally for binding work and enum maintenance:
uv run python scripts/sync_expedition_headers.py
uv run python scripts/check_enums_against_headers.py
- Headers live under
reference/expedition/(gitignored). Seereference/README.md. - Do not commit headers or bundle them in the wheel.
CoreMem.his not shipped with Expedition; channel layout comes fromuser_channels.h/sys_channels.h.- After an Expedition upgrade: sync headers →
generate_enums_from_headers.py --write→ check-enums → reviewExpDLL.hexports → verifyValTypeinExpedition/exval.pyagainste_ValTypeifsys_val.h/time_dev.hchanged → updatedll_wrapper.pyif needed → run tests.
Enum naming (2.0+)
Python enum members use mechanical names from the C headers (no override tables):
| C enum | Strip prefix | Example |
|---|---|---|
ExChannels |
Ex |
ExLwy → Lwy |
ExSysChannels |
ExSys (or Ex for ExNumSysChannels) |
ExSysMouseTime → MouseTime |
ExSysBooleanChannels |
ExSysBool |
ExSysBoolAutoPan → AutoPan |
ExSysIntChannels |
ExSysInt |
ExSysIntTheme → Theme |
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.
- 2d ago First seen · 106 lines · 1,402 tokens per session scan A 547d22bac697
Expedition-Python AGENTS.md is an instructions file published in the GitHub repository TTCMarine/Expedition-Python (10 stars, last pushed 1mo ago), licensed MIT. It adds 1,402 tokens to every session, about $0.0070 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.