What is mcp_rfq_processor AGENTS.md?

Repository-specific instructions for the mcp_rfq_processor project, a Python service that processes requests for quotations and related pricing information. They describe its structure, setup, commands, coding style, and tests.

Use them when installing the project, launching its local server, editing its Python modules, formatting code with Black, or running pytest tests and coverage.

They give an agent the project rules needed to make changes that fit the repository and to run its build, formatting, and test checks.

How ideabosque/mcp_rfq_processor configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to ideabosque/mcp_rfq_processor. 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/ideabosque/mcp_rfq_processor/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/ideabosque/mcp_rfq_processor

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/ideabosque/mcp_rfq_processor/agents-md/github.svg)](https://agentmods.dev/instructions/ideabosque/mcp_rfq_processor/agents-md)

Your own site

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

Per session 662 This file is loaded in full into every session.

When invoked 662 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.00662	$0.00662
Opus 5.5	$0.00265	$0.00265
Sonnet 5.5	$0.00132	$0.00132
Haiku 4.5	$0.00066	$0.00066

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

Security

Grade A, and why

mcp_rfq_processor 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 2mo 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 · 36 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

Core package lives in mcp_rfq_processor/; each *_processor.py module wraps a specific RFQ domain (request, quote, pricing, installments, files, segments) and is orchestrated by mcp_rfq_processor.py via MCPRfqProcessor.
GraphQL client and helpers sit in graphql_backed_processor.py and graphql_client.py, with status logic in status_manager.py.
Tests and fixtures are under mcp_rfq_processor/tests/ (test_mcp_rfq_processor.py, test_data.json). API and workflow docs are in API_REFERENCE.md and DEVELOPMENT_PLAN.md.

Build, Test, and Development Commands

Install in editable mode: pip install -e .[dev] (run from repo root; pulls pytest/black). For runtime-only: pip install -e ..
Launch server locally: python -m mcp_rfq_processor after setting required env vars (see README configuration).
Run tests: pytest -q or pytest -q --cov=mcp_rfq_processor --cov-report=term-missing for coverage.
Format: black . (88-char width, Python 3.8 target).

Coding Style & Naming Conventions

Python 3.8+, Black-formatted (88 chars). Prefer type hints on public methods; match existing patterns in processors.
Use snake_case for functions/variables, PascalCase for classes, and UPPER_SNAKE for constants/status values.
Keep GraphQL operation names and note strings consistent with DEVELOPMENT_PLAN.md status rules.
Log through the provided logger; avoid bare prints.

Testing Guidelines

Add/extend tests in mcp_rfq_processor/tests/test_mcp_rfq_processor.py; reuse/extend test_data.json fixtures.
Name tests test_* and structure with clear Arrange/Act/Assert blocks.
Validate status transitions, auto-complete/disapprove flows, and error paths; prefer explicit assertions on returned status and notes.
Run pytest -q before pushing; include coverage run when altering workflow logic.

Commit & Pull Request Guidelines

Follow conventional-style prefixes observed in history (feat:, fix:, chore:). Keep summaries imperative and under ~72 chars.
Each PR should describe behavior changes, affected tools, and checklist of tests run; link related issues/tickets.
Include repro steps or sample payloads for behavior changes (e.g., request/quote IDs used) and note config/ENV variable impacts.
Screenshots are unnecessary; prefer concise notes or log excerpts for failures.

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

2mo ago First seen · 36 lines · 662 tokens per session scan A d6ba02856bfd

Subscribe to this mod's changes

mcp_rfq_processor AGENTS.md is an instructions file published in the GitHub repository ideabosque/mcp_rfq_processor (0 stars, last pushed 3mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0026 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-31.

mcp_rfq_processor AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp_rfq_processor AGENTS.mdideabosque/mcp_rfq_processor	Instructions file	0	3mo ago	MIT	A	662	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

mcp_rfq_processor: Instructions file for Codex