owd-albatross

A legacy connection guide for linking an Albatross agent workspace to MDevolved. Albatross runs local agents and tools, while MDevolved manages shared projects, approvals, project context, and handoffs.

In plain words
What is it for?
Use it to configure the older connection, authenticate through its bridge, resume or coordinate MDevolved Projects, and maintain project context across Albatross sessions.
Why use it?
It gives older Albatross setups a defined connection method without changing MDevolved’s access rules or project lifecycle. It also helps preserve existing workspace settings and identify contributors separately.

Skill for Claude CodeCodex

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 skills/msinclair25/mdevolved/owd-albatross
Any agent
npx skills add msinclair25/mdevolved --skill owd-albatross
Clone the repo
git clone --depth 1 https://github.com/msinclair25/mdevolved

Made for: Claude Code, Codex.

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,628 The whole file, excluding the scripts and references it only reads on demand.
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.00093 $0.01628
Opus 5 $0.00046 $0.00814
Sonnet 5 $0.00019 $0.00326
Haiku 4.5 $0.00009 $0.00163

Measured yesterday against content hash 7bfe57292e0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

owd-albatross 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 yesterday.

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.

packages/client-packs/owd-albatross/SKILL.md · 144 lines

How it starts

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

MDevolved + Albatross

Legacy compatibility path. New setups should use mdevolved-albatross; keep this pack for existing owd configurations and receipts.

Keep one universal MDevolved server. Apply this profile only as Albatross-side configuration and instructions; never change MDevolved framing, OAuth, tool schemas, Project lifecycle, or server-side authority.

Confirm the runtime

  1. Confirm the repository uses Albatross and inspect agent.config.json, .albatross/prompt.md, .owdignore, and AGENTS.md when present.
  2. Preserve every existing Albatross option and MCP server.
  3. Use the deployment's exact HTTPS /mcp URL. Plain HTTP is allowed only for localhost development.
  4. Use MCP server name owd; Albatross exposes its tools as mcp__owd__<tool>.

Albatross 2.0.3 supports child-process stdio MCP only. Use the profile's pinned [email protected] bridge with --transport http-only. This is a temporary client adapter, not an MDevolved proxy or protocol fork. Remove it when Albatross supports authenticated remote Streamable HTTP natively.

Do not add a static bearer token, custom Project call, translated tool schema, client-side authorization rule, or a second MDevolved endpoint.

Preserve participant identity

The bridge configuration includes a non-secret X-OWD-Albatross-Participant header. The pinned bridge includes custom headers in its OAuth cache key:

  • Reusing primary means the Albatross sessions are one MDevolved OAuth participant.
  • A genuinely independent writer or reviewer uses another safe ID such as reviewer and completes a separate authorization.
  • A new session, /reset, path fork, model, or display name using the same ID is still the same MDevolved participant.

The header partitions local credential storage; it is not a credential and grants no access. MDevolved OAuth identity and live server-side grants remain authoritative.

Install without overwriting

Prefer the authenticated MDevolved dashboard's Copy Albatross setup kit action. It generates one fresh, internally consistent participant ID across these steps. Choose New participant ID before copying a kit for another workspace or independently attributable reviewer.

Read the full file on GitHub · 144 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 144 lines · 93 tokens per session scan A 7bfe57292e0d

Subscribe to this mod's changes

owd-albatross is a skill published in the GitHub repository msinclair25/mdevolved (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 93 tokens to every session and 1,628 once invoked, about $0.0005 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-09-01.

Related

Other skills, from other repositories

backups

Use when designing or auditing a backup-and-restore program that must survive a real disaster: setting defensible RPO/RTO targets, laying out 3-2-1-1-0 copies that are offsite and immutable, wiring point-in-time recovery, and proving restores work on a schedule. NOT tuning Postgres internals or writing the…

ericrisco/rsc-harness · 82 tokens

tfw-identity

Внутренний fail-closed механизм профилей и локальной привязки Assisted; отделяет участника, роли, task owner и роль ИИ.

saubakirov/trace-first-starter · 37 tokens

tfw-config

Command /tfw-config audits or changes Trace-First Workflow configuration and propagates values to every registered inline location. Use for /tfw-config, config verification, projectconfig.yaml changes, or Config Sync Registry updates.

saubakirov/trace-first-starter · 48 tokens

tfw-handoff

Command /tfw-handoff executes an approved Trace-First Workflow TS and creates ONB, implementation changes, evidence, and RF. Use for /tfw-handoff or implementation of an approved TFW task or phase.

saubakirov/trace-first-starter · 50 tokens

tfw-init

Command /tfw-init initializes Trace-First Workflow or attaches and repairs TFW tooling in an existing project. Use for /tfw-init, first-time setup, project discovery, adapter installation, or Codex adapter repair.

saubakirov/trace-first-starter · 49 tokens

tfw-knowledge

Command /tfw-knowledge consolidates Trace-First Workflow Fact Candidates into verified project knowledge. Use for /tfw-knowledge, the knowledge gate, fact promotion, topic files, or knowledgestate.yaml maintenance.

saubakirov/trace-first-starter · 48 tokens