What is mayros AGENTS.md?

Repository instructions for Mayros, covering its code layout, tests, documentation, extensions, installers, and contribution rules.

Use it when editing Mayros source code, tests, Mintlify documentation, internationalized docs, extensions, or installer files.

It gives an agent the project-specific rules needed to make changes in the right places and avoid breaking its packaging or documentation setup.

How ApiliumCode/mayros configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ApiliumCode/mayros. 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/ApiliumCode/mayros/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ApiliumCode/mayros

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/apiliumcode/mayros/agents-md/github.svg)](https://agentmods.dev/instructions/apiliumcode/mayros/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/apiliumcode/mayros/agents-md"><img src="https://agentmods.dev/badge/instructions/apiliumcode/mayros/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/apiliumcode/mayros/agents-md"><img src="https://agentmods.dev/badge/instructions/apiliumcode/mayros/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5,416 This file is loaded in full into every session.

When invoked 5,416 The same file — it is already loaded in full.

Security scan B 1 finding. 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.05416	$0.05416
Opus 5.5	$0.02166	$0.02166
Sonnet 5.5	$0.01083	$0.01083
Haiku 4.5	$0.00542	$0.00542

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

Security

Grade B, and why

mayros AGENTS.md scanned grade B with 1 finding 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Update: `sudo npm i -g mayros@latest` (global install needs root on `/usr/lib/node_modules`).

AGENTS.md · 240 lines

How it starts

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

Repository Guidelines

Repo: https://github.com/ApiliumCode/mayros
GitHub issues/comments/PR comments: use literal multiline strings or -F - <<'EOF' (or $'...') for real newlines; never embed "\n".

Project Structure & Module Organization

Source code: src/ (CLI wiring in src/cli, commands in src/commands, web provider in src/provider-web.ts, infra in src/infra, media pipeline in src/media).
Tests: colocated *.test.ts.
Docs: docs/ (images, queue, Pi config). Built output lives in dist/.
Plugins/extensions: live under extensions/* (workspace packages). Keep plugin-only deps in the extension package.json; do not add them to the root package.json unless core uses them.
Plugins: install runs npm install --omit=dev in plugin dir; runtime deps must live in dependencies. Avoid workspace:* in dependencies (npm install breaks); put mayros in devDependencies or peerDependencies instead (runtime resolves mayros/plugin-sdk via jiti alias).
Installers served from https://maryos.apilium.com/*: live in the sibling repo ../maryos-cli-install (public/install.sh, public/install-cli.sh, public/install.ps1).
Messaging channels: always consider all built-in + extension channels when refactoring shared logic (routing, allowlists, pairing, command gating, onboarding, docs).
- Core channel docs: docs/channels/
- Core channel code: src/telegram, src/discord, src/slack, src/signal, src/imessage, src/web (WhatsApp web), src/channels, src/routing
- Extensions (channel plugins): extensions/* (e.g. extensions/msteams, extensions/matrix, extensions/zalo, extensions/zalouser, extensions/voice-call)
When adding channels/extensions/apps/docs, update .github/labeler.yml and create matching GitHub labels (use existing channel/extension label colors).

Docs Linking (Mintlify)

Docs are hosted on Mintlify (apilium.com/us/doc/maryos).
Internal doc links in docs/**/*.md: root-relative, no .md/.mdx (example: [Config](/configuration)).
When working with documentation, read the mintlify skill.
Section cross-references: use anchors on root-relative paths (example: [Hooks](/configuration#hooks)).
Doc headings and anchors: avoid em dashes and apostrophes in headings because they break Mintlify anchor links.
When Peter asks for links, reply with full https://apilium.com/us/doc/maryos/... URLs (not root-relative).
When you touch docs, end the reply with the https://apilium.com/us/doc/maryos/... URLs you referenced.
README (GitHub): keep absolute docs URLs (https://apilium.com/us/doc/maryos/...) so links work on GitHub.
Docs content must be generic: no personal device names/hostnames/paths; use placeholders like user@gateway-host and “gateway host”.

Read the full file on GitHub · 240 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 · 240 lines · 5,416 tokens per session scan B dcf126655339

Subscribe to this mod's changes

mayros AGENTS.md is an instructions file published in the GitHub repository ApiliumCode/mayros (13 stars, last pushed 3mo ago), licensed MIT. It adds 5,416 tokens to every session, about $0.0217 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

agent-mesh agent-orchestration agentic-ai ai-agent-platform ai-agents ai-memory

mayros AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mayros AGENTS.mdApiliumCode/mayros	Instructions file	13	3mo ago	MIT	B	5,416	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

mayros: Instructions file for Codex