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.
npx agentmods add instructions/apiliumcode/mayros/agents-mdgit clone --depth 1 https://github.com/ApiliumCode/mayrosWhat 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 | $0.05416 | $0.05416 |
| Opus 5 | $0.02708 | $0.02708 |
| Sonnet 5 | $0.01083 | $0.01083 |
| Haiku 4.5 | $0.00542 | $0.00542 |
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`). 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 insrc/cli, commands insrc/commands, web provider insrc/provider-web.ts, infra insrc/infra, media pipeline insrc/media). - Tests: colocated
*.test.ts. - Docs:
docs/(images, queue, Pi config). Built output lives indist/. - Plugins/extensions: live under
extensions/*(workspace packages). Keep plugin-only deps in the extensionpackage.json; do not add them to the rootpackage.jsonunless core uses them. - Plugins: install runs
npm install --omit=devin plugin dir; runtime deps must live independencies. Avoidworkspace:*independencies(npm install breaks); putmayrosindevDependenciesorpeerDependenciesinstead (runtime resolvesmayros/plugin-sdkvia 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)
- Core channel docs:
- When adding channels/extensions/apps/docs, update
.github/labeler.ymland 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-hostand “gateway host”.
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.
- yesterday First seen · 240 lines · 5,416 tokens per session scan B dcf126655339
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.
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.
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?
tpu_performance_autoresearch_wiki AGENTS.md
Instructions for vlasenkoalexey/tpu_performance_autoresearch_wiki, covering codex instructions, compatibility, operating rules and codex translation notes.
powernode-platform CLAUDE.md
Instructions for nodealchemy/powernode-platform, covering claude.md, project overview, core models, where guidance lives and memory & knowledge.
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).
zaivern-code CLAUDE.md
Instructions for tacyan/zaivern-code, covering claude.md — zaivern code 開発ガイド(aiエージェント向け), 絶対ルール, ui 文字列と多言語 (language pack), テストと検証 and ui の原則.