agentmods.dev

manta: Instructions file for Codex

AGENTS.md

manta AGENTS.md is an instructions file for Codex, OpenCode from manta-ide/manta. It costs 585 tokens per session, scanned A, original, MIT.

Repository instructions for a manta application built with Next.js and TypeScript. They describe where pages, API routes, components, hooks, utilities, public files, and helper scripts belong, along with commands for development, building, and linting.

In plain words
What is it for?
Use them when adding or changing routes, components, hooks, utilities, API handlers, or public assets, and when running the app’s development, build, or lint commands.
Why use it?
They give an AI coding agent the project’s expected structure and conventions before it changes code. This helps keep new work consistent with the existing application and makes the provided checks easier to run.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is manta-ide/manta's own configuration. It tells Codex and OpenCode how to work on manta itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything manta configures →

not rated 75repo 2mo ago A scan 585 tokens original MIT
View source ↗ manta-ide/manta getmanta.ai
Reuse

Borrowing it

Nothing to install: this file belongs to manta-ide/manta. 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/manta-ide/manta/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/manta-ide/manta

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.

agentmods badge for manta AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/manta-ide/manta/agents-md/github.svg)](https://agentmods.dev/instructions/manta-ide/manta/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/manta-ide/manta/agents-md"><img src="https://agentmods.dev/badge/instructions/manta-ide/manta/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.

agentmods 80×15 button for manta AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/manta-ide/manta/agents-md"><img src="https://agentmods.dev/badge/instructions/manta-ide/manta/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 585 This file is loaded in full into every session.
When invoked 585 The same file — it is already loaded in full.
Security scan A 0 findings. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00585 $0.00585
Opus 5.5 $0.00234 $0.00234
Sonnet 5.5 $0.00117 $0.00117
Haiku 4.5 $0.00059 $0.00059

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

Security

Grade A, and why

manta 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 1mo 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.

AGENTS.md · 47 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • Root app: Next.js (TypeScript) in src with App Router.
    • UI in src/components, hooks in src/hooks, utilities in src/lib.
    • Routes: pages under src/app (e.g., page.tsx), API under src/app/api/*.
  • Public assets in public/.
  • Helper scripts in scripts/ (e.g., scripts/setup-db.ts).
  • Vite template in vite-base-template/ (standalone dev environment).

Build, Test, and Development Commands

  • Root app:
    • npm run dev — start Next.js with Turbopack on http://localhost:3000.
    • npm run build — production build.
    • npm run start — run built app.
    • npm run lint — ESLint checks.
  • Vite template:
    • cd vite-base-template && npm run dev — start Vite (default :5173).
    • npm --prefix vite-base-template run build — build Vite app.

Coding Style & Naming Conventions

  • Language: TypeScript (strict enabled, noEmit: true). Path alias @/* → src/*.
  • Linting: Next.js + TypeScript config (eslint.config.mjs); @typescript-eslint/no-explicit-any is disabled.
  • Indentation: 2 spaces. Components in PascalCase, variables/functions in camelCase, files in kebab-case (Next.js conventions like page.tsx, route.ts).
  • Styling: Tailwind CSS v4 is configured.

Testing Guidelines

  • No test runner is currently configured. Prefer:
    • Unit/UI: Vitest or Jest + React Testing Library.
    • E2E: Playwright.
  • Place tests next to source: Component.test.tsx or under __tests__/.
  • Aim for critical-path coverage (core components, API handlers).

Commit & Pull Request Guidelines

  • Commit messages: imperative, concise, scoped if helpful.
    • Examples: feat(editor): add split panes, fix(api): handle 500 on export.
  • PRs must include:
    • Summary of changes and rationale.
    • Steps to test locally; attach screenshots for UI changes.
    • Linked issue(s) and checklist: builds, lints, and runs locally.

Security & Configuration Tips

  • Environment: use .env.local for developer machines; do not commit secrets.
  • Key vars: NEXT_PUBLIC_* are client-exposed.
  • Rotate any leaked credentials promptly; prefer per-env keys.
  • Proxy/iframe: app rewrites /iframe/* to a dynamic API (src/app/api/iframe).

Read the full file on GitHub · 47 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. 1mo ago First seen · 47 lines · 585 tokens per session scan A 774ede7381c3

Subscribe to this mod's changes

manta AGENTS.md is an instructions file published in the GitHub repository manta-ide/manta (75 stars, last pushed 2mo ago), licensed MIT. It adds 585 tokens to every session, about $0.0023 per session on Opus 5.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.

Claude Codeaiai-agentsartificial-intelligenceclaudeclaude-ai
Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

vscode model-prompts.instructions.md

Model-specific prompt authoring and registry guidelines.

microsoft/vscode · 2,022 tokens