Albatross AGENTS.md

Albatross AGENTS.md is an instructions file for Codex, OpenCode from morganlinton/Albatross. It costs 454 tokens per session, scanned A, original, MIT.

Contributor and release instructions for Albatross, including required checks and the steps for publishing a version.

In plain words
What is it for?
Use them when changing the project, preparing a release, running Rust formatting, linting and tests, or confirming a GitHub and Homebrew release.
Why use it?
They prevent a release from being treated as complete before its code checks, version tag, automated workflow, and macOS files are verified.

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

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 Albatross AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/morganlinton/albatross/agents-md.svg)](https://agentmods.dev/instructions/morganlinton/albatross/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/morganlinton/albatross/agents-md"><img src="https://agentmods.dev/badge/instructions/morganlinton/albatross/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 454 This file is loaded in full into every session.
When invoked 454 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.00454 $0.00454
Opus 5 $0.00227 $0.00227
Sonnet 5 $0.00091 $0.00091
Haiku 4.5 $0.00045 $0.00045

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

Security

Grade A, and why

Albatross 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 5d 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 · 42 lines

What it actually says

Agent Instructions

General

  • After finishing code or documentation updates, give the user a git commit message.
  • Before pushing to main, run the CI check suite:
    cargo fmt --all -- --check
    cargo clippy --all-targets -- -D warnings
    cargo test
    
    Tests passing alone is not the release bar; clippy with -D warnings must pass.

Releases

Updating Cargo.toml, Cargo.lock, README.md, and CHANGELOG.md is not shipping a release. A version is released only after the vX.Y.Z tag exists, the GitHub Release workflow succeeds, and macOS assets are published.

Full step-by-step: docs/RELEASE.md

Summary:

  1. Confirm with the user: land on main only, or ship release X.Y.Z.
  2. Prefer separate commits: feature work first, then chore: release X.Y.Z.
  3. Push main, create and push tag vX.Y.Z, watch .github/workflows/release.yml.
  4. Verify: gh release view vX.Y.Z (release exists, macOS assets present).
  5. Verify Homebrew tap: morganlinton/homebrew-tapFormula/albatross.rb matches the version. Optionally test brew upgrade albatross.

Do not mark release work complete until step 4 succeeds.

Scorecard (when changing /scorecard or ship quality scoring)

  • Distinguish numeric score (0–100) from counts (increments “quality PRs shipped” on the grid). If manual /scorecard close --url --tests is documented as a quality ship path, add tests that counts is true when evidence warrants it — not only that the score looks good.
  • Manual closes use opened_by_gh: false; grid logic must align with --url and test evidence unless docs explicitly say manual closes are score-only.
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. 5d ago First seen · 42 lines · 454 tokens per session scan A b48b673ec498

Subscribe to this mod's changes

Albatross AGENTS.md is an instructions file published in the GitHub repository morganlinton/Albatross (226 stars, last pushed 10d ago), licensed MIT. It adds 454 tokens to every session, about $0.0023 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-30.