What is modelrelay AGENTS.md?

A set of development and release instructions for ModelRelay, a software project that requires its full test suite after changes. It also defines how version numbers are increased and how release commits are written.

Use it after implementing a feature or fix, when preparing a release, when checking the current version history, and when committing all release changes.

It makes testing and release steps predictable instead of leaving them to individual judgment. This helps catch regressions and avoids inconsistent version bumps or commit messages.

How ellipticmarketing/modelrelay configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ellipticmarketing/modelrelay. 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/ellipticmarketing/modelrelay/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ellipticmarketing/modelrelay

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ellipticmarketing/modelrelay/agents-md/github.svg)](https://agentmods.dev/instructions/ellipticmarketing/modelrelay/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ellipticmarketing/modelrelay/agents-md"><img src="https://agentmods.dev/badge/instructions/ellipticmarketing/modelrelay/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ellipticmarketing/modelrelay/agents-md"><img src="https://agentmods.dev/badge/instructions/ellipticmarketing/modelrelay/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,514 This file is loaded in full into every session.

When invoked 1,514 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.01514	$0.01514
Opus 5.5	$0.00606	$0.00606
Sonnet 5.5	$0.00303	$0.00303
Haiku 4.5	$0.00151	$0.00151

Measured 2mo ago against content hash 09b42f1ac8b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

modelrelay 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 2mo 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 · 106 lines

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 Instructions

Post-Feature Testing

After completing any feature or fix, the agent MUST:

Run pnpm test to verify the complete unit-test suite passes
If any test fails, fix the issue immediately
Re-run pnpm test until all tests pass

This ensures the codebase remains in a working state at all times.

Git Commits

When making a commit on behalf of the user, NEVER prefix your commit message with fix:, feature:, feat:, chore:, or any other prefix. Just write a descriptive sentence of what was changed.

Release Process (MANDATORY)

When releasing a new version, follow this exact process:

Version Check: Check if version already exists with git log --oneline | grep "^[a-f0-9]\+ [0-9]"
Version Bump: Update version in package.json. If the releas only includes bug fixes, bump a patch version (e.g., 0.1.16 → 0.1.17). If it includes new features, bump a minor version (e.g., 0.1.16 → 0.2.0) Do not bump the major version.
Commit ALL Changed Files: git add . && git commit -m "Fixed issue with autostart"
- Always commit using a description of what was changed as the commit message.
- Include ALL modified files in the commit (bin/, lib/, test/, README.md, etc.)
Push: git push origin master — this repo's release branch is master, and GitHub Actions will auto-publish to npm
Create GitHub Release:
```
gh release create VERSION --title "VERSION" --notes "Release notes"
```
(e.g., gh release create 1.5.0 --title "1.5.0" --notes "Fixed an issue with ABC") When writing the release notes, summarize the changes from all commits since the last release.

**Wait for npm Publish":

for i in $(seq 1 30); do sleep 10; v=$(npm view modelrelay version 2>/dev/null); echo "Attempt $i: npm version = $v"; if [ "$v" = "0.1.17" ]; then echo "✅ published!"; break; fi; done

Install and Verify: npm install -g [email protected]
Test Binary: modelrelay --help (or any other command to verify it works)
Only when the global npm-installed version works → the release is confirmed

Read the full file on GitHub · 106 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.

2mo ago First seen · 106 lines · 1,514 tokens per session scan A 09b42f1ac8b2

Subscribe to this mod's changes

modelrelay AGENTS.md is an instructions file published in the GitHub repository ellipticmarketing/modelrelay (344 stars, last pushed 1mo ago), licensed MIT. It adds 1,514 tokens to every session, about $0.0061 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-08-30.

Commits Git and workflow Releases

modelrelay AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
modelrelay AGENTS.mdellipticmarketing/modelrelay	Instructions file	344	1mo ago	MIT	A	1,514	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

modelrelay: Instructions file for Codex