What is MCP-Server-Totvs-Moda AGENTS.md?

A set of development instructions for the TOTVS Moda MCP server, including conventions for API endpoints, dates, fields, and large file outputs.

Use it when developing or changing TOTVS Moda MCP tools, especially date filters, field selection, write operations, product images, PDF output, and accounts-receivable handling.

It helps contributors follow the project’s established implementation and response patterns, reducing inconsistent behaviour and oversized tool responses.

How fabianoomura/MCP-Server-Totvs-Moda configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to fabianoomura/MCP-Server-Totvs-Moda. 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/fabianoomura/MCP-Server-Totvs-Moda/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/fabianoomura/MCP-Server-Totvs-Moda

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/fabianoomura/mcp-server-totvs-moda/agents-md/github.svg)](https://agentmods.dev/instructions/fabianoomura/mcp-server-totvs-moda/agents-md)

Your own site

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

Per session 1,264 This file is loaded in full into every session.

When invoked 1,264 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.

Model	Per session	Once invoked
Fable 5.1	$0.01264	$0.01264
Opus 5	$0.00632	$0.00632
Sonnet 5	$0.00253	$0.00253
Haiku 4.5	$0.00126	$0.00126

Measured 9d ago against content hash 3842e84c0fec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

MCP-Server-Totvs-Moda 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

MCP-Server-Totvs-Moda CLAUDE.md — 100% identical, 0 lines differ

AGENTS.md · 93 lines

How it starts

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

TOTVS Moda MCP — Instruções de desenvolvimento

Convenções de DX (v3.11+)

Padrões adotados para tornar as respostas mais úteis a um LLM. Ao criar/alterar tools, seguir:

Saída de arquivos grandes — payloads binários (PDF/imagem) não devem voltar como base64 inline (estoura o limite de tokens). Use tools/_output.py: save_base64() grava na pasta resolvida por resolve_output_dir() (TOTVS_OUTPUT_DIR → Downloads → home → temp) e retorna o caminho. Exponha uma flag returnBase64 para o conteúdo cru. Aplicado em get_danfe e search_product_images.
Filtros de data de "dia" — em buscas com start*/end*Date, chame tools/_dates.normalize_day_ranges(args) logo após inject_branch_defaults. Uma data única (start == end, date-only) é expandida para o dia inteiro, contornando o GeneralGreaterThan da API.
Validação de fields= — apply_fields anexa _fieldsWarning quando um nome não casa com a resposta (em vez de retornar vazio). Mantenha pick_fields puro; a validação fica no wrapper. Campos que confundem ficam em docs/FIELDS.md — atualize lá ao descobrir novos.
Contas a receber (venda x recebimento) — billingType separa o lado venda (1/2 = a receber) do recebimento/caixa (3/4). Nunca some os dois. O opt-in withStatusFlags marca billingSide/isOpen/isSettled/openValue e devolve receivableSummary {open, settled, receiptSide}.
Visões compactas (*_360) — quando a fonte de produtos não traz valores (ex.: /invoice-products/search), enriqueça a partir dos itens da nota (expand=items, netValue/unitNetValue) antes de retornar.

Documentação destas convenções vive em 3 lugares (manter sincronizado ao mudar comportamento): descrição das tools em tools/*.py, guia em server._build_instructions() / _build_connect_instructions(), e docs/FIELDS.md.

Padrão para endpoints de escrita

Create → fallback para Update

Ao implementar um endpoint de inclusão (create/incluir), sempre tratar o caso em que o registro já existe:

Read the full file on GitHub · 93 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.

9d ago First seen · 93 lines · 1,264 tokens per session scan A 3842e84c0fec

Subscribe to this mod's changes

MCP-Server-Totvs-Moda AGENTS.md is an instructions file published in the GitHub repository fabianoomura/MCP-Server-Totvs-Moda (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,264 tokens to every session, about $0.0063 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-31.

Backend and APIs Claude Code brasil claude-ai erp fashion mcp-server

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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 · 6,785 tokens

MCP-Server-Totvs-Moda: Instructions file for Codex