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/pasta-devs/marinara-engine/agents-mdgit clone --depth 1 https://github.com/Pasta-Devs/Marinara-EngineWhat 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.02018 | $0.02018 |
| Opus 5 | $0.01009 | $0.01009 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
Marinara-Engine 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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 96 lines · 2,018 tokens per session scan A 93460cea4850
Marinara-Engine AGENTS.md is an instructions file published in the GitHub repository Pasta-Devs/Marinara-Engine (615 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 2,018 tokens to every session, about $0.0101 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.
Other instructions, from other repositories
AutoAgents AGENTS.md
Instructions for liquidos-ai/AutoAgents, covering autoagents repository guidelines, project structure & module organization, code quality, naming conventions and error handling.
local-operator AGENTS.md
Instructions for damianvtran/local-operator, covering working on local-operator, environment, releasing the stable lop runtime, versioning: choose the bump by materiality, not commit type and visual validation: how to actually look at a ui change.
ontology-atlas AGENTS.md
Instructions for wlsdks/ontology-atlas, covering agents.md — ontology-atlas, product and non-negotiable architecture, start here, structure and routes and operating gates and skills.
oneringai CLAUDE.md
Instructions for aantich/oneringai: AGENTS.md is the canonical OneRingAI guide for every coding agent.
ontology-atlas CLAUDE.md
Instructions for wlsdks/ontology-atlas, covering claude.md, visibility and mirrors, claude code loading and synchronization.
Agentflow CLAUDE.md
Instructions for 10xHub/Agentflow, covering agentflow (core python library) — engineering guide, what this package is, working principles for this codebase, package layout (real, current) and import map (verified) — this is the part that bites people.