agentmods.dev

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.

In plain words
What is it for?
Use them when installing the project, launching its local server, editing its Python modules, formatting code with Black, or running pytest tests and coverage.
Why use it?
They give an agent the project rules needed to make changes that fit the repository and to run its build, formatting, and test checks.

Instructions file for CodexOpenCode

0 1mo ago A scan 662 tokens original MIT
View the source file ideabosque/mcp_rfq_processor
Install

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.

agentmods
npx agentmods add instructions/ideabosque/mcp_rfq_processor/agents-md
Clone the repo
git clone --depth 1 https://github.com/ideabosque/mcp_rfq_processor

Made for: Codex, OpenCode.

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. Scan, not verified.
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 $0.00662 $0.00662
Opus 5 $0.00331 $0.00331
Sonnet 5 $0.00132 $0.00132
Haiku 4.5 $0.00066 $0.00066

Measured yesterday against content hash d6ba02856bfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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.

  1. yesterday 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 1mo ago), licensed MIT. It adds 662 tokens to every session, about $0.0033 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.

LanguagesTesting
Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 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

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,182 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,345 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js 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