mayros AGENTS.md

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

In plain words
What is it for?
Use it when editing Mayros source code, tests, Mintlify documentation, internationalized docs, extensions, or installer files.
Why use it?
It gives an agent the project-specific rules needed to make changes in the right places and avoid breaking its packaging or documentation setup.

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/apiliumcode/mayros/agents-md
Clone the repo
git clone --depth 1 https://github.com/ApiliumCode/mayros

Made for: Codex, OpenCode.

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. 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.05416 $0.05416
Opus 5 $0.02708 $0.02708
Sonnet 5 $0.01083 $0.01083
Haiku 4.5 $0.00542 $0.00542

Measured yesterday against content hash dcf126655339, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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

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.

  1. yesterday 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 (12 stars, last pushed 1mo ago), licensed MIT. It adds 5,416 tokens to every session, about $0.0271 per session on Opus 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.

Related

Other instructions, from other repositories

obsidian-wiki AGENTS.md

AGENTS.md instructions for Ar9av/obsidian-wiki, covering obsidian wiki — agent context, readme translation parity, configuration, targeting a specific vault and vault structure.

Ar9av/obsidian-wiki · 3,876 tokens

claudette regression-review.instructions.md

Instructions for utensils/claudette: When reviewing or generating a PR, explicitly look for regressions before style issues. Ask: what existing user workflow, persisted value, IPC contract, CLI command, plugin API, terminal behavior, worktree operation, or localization path could this change break?

utensils/claudette · 349 tokens

tpu_performance_autoresearch_wiki AGENTS.md

Instructions for vlasenkoalexey/tpu_performance_autoresearch_wiki, covering codex instructions, compatibility, operating rules and codex translation notes.

vlasenkoalexey/tpu_performance_autoresearch_wiki · 436 tokens

powernode-platform CLAUDE.md

Instructions for nodealchemy/powernode-platform, covering claude.md, project overview, core models, where guidance lives and memory & knowledge.

nodealchemy/powernode-platform · 3,514 tokens

genasis CLAUDE.md

Instructions for claude-genasis/genasis, covering claude.md — project instructions for genasis, core philosophy — the north star, how to apply this philosophy, bilingual mirror policy and mirror pairs (authoritative list).

claude-genasis/genasis · 4,742 tokens

zaivern-code CLAUDE.md

Instructions for tacyan/zaivern-code, covering claude.md — zaivern code 開発ガイド(aiエージェント向け), 絶対ルール, ui 文字列と多言語 (language pack), テストと検証 and ui の原則.

tacyan/zaivern-code · 19,910 tokens