What is prefect-mcp-server AGENTS.md?

Repository instructions for developing prefect-mcp-server, a server that exposes Prefect tools for automation and workflow management. Prefect is a platform for running and monitoring data workflows.

They help organize the Python package, run tests and builds, use the command-line entry point, follow naming rules, and work with a live Prefect account.

They give developers a shared structure and command baseline for building, testing, packaging, and documenting the server. They also clarify how live Prefect access is configured.

How fortunto2/prefect-mcp-server configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to fortunto2/prefect-mcp-server. 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/fortunto2/prefect-mcp-server/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/fortunto2/prefect-mcp-server

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

Your own site

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

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

When invoked 593 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.00593	$0.00593
Opus 5.5	$0.00237	$0.00237
Sonnet 5.5	$0.00119	$0.00119
Haiku 4.5	$0.00059	$0.00059

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

Security

Grade A, and why

prefect-mcp-server 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

prefect_mcp_server_pkg/ contains the runtime package; server.py exposes all MCP tools and the console entry point defined in pyproject.toml.
docs/prefect_mcp_documentation.md captures user-facing behavior; update it alongside feature changes.
Makefile, pyproject.toml, and uv.lock manage builds and dependencies; never edit uv.lock by hand.
dist/ is generated output from packaging; remove artifacts with make clean before committing.

Build, Test, and Development Commands

make build (wraps uv build) packages the project for distribution and refreshes dist/.
make test runs pytest; use it before every push even if no dedicated tests exist yet.
uv run prefect-mcp-server --help exercises the CLI entry point locally. Provide PREFECT_API_URL and PREFECT_API_KEY in your shell when hitting a live Prefect instance.
make clean clears build outputs to ensure reproducible artifacts.

Coding Style & Naming Conventions

Follow existing 4-space indentation and type-hinted async APIs as shown in prefect_mcp_server_pkg/server.py.
Use snake_case for functions/tools (get_flow_by_id) and SCREAMING_SNAKE_CASE for module-level constants (PREFECT_API_URL).
Prefer descriptive docstrings and in-line logging over comments; keep responses JSON-serializable for MCP clients.
Run uv run python -m compileall prefect_mcp_server_pkg if you need a quick syntax check without tests.

Testing Guidelines

Tests should live under tests/ and mirror tool modules (e.g., tests/test_flows.py).
Name tests test_<behavior> and mock Prefect clients to avoid contacting real services.
Use pytest.mark.asyncio for coroutine-based cases and assert on serialized dictionaries returned to MCP.
Aim to exercise error paths (missing IDs, Prefect API failures) before feature merges.

Commit & Pull Request Guidelines

Use focused commit headers similar to existing history (Fix: Use correct filter parameters…) and limit scopes to a single concern.
Reference related Prefect tickets or MCP issues in the body and note environment variables touched.
Pull requests should include: summary of changes, testing commands executed, configuration prerequisites, and screenshots or terminal snippets when behavior is user-visible.
Keep PRs small; coordinate larger efforts with maintainers via an outline in the description.

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 · 593 tokens per session scan A 9fb58c57af73

Subscribe to this mod's changes

prefect-mcp-server AGENTS.md is an instructions file published in the GitHub repository fortunto2/prefect-mcp-server (7 stars, last pushed 1y ago), licensed MIT. It adds 593 tokens to every session, about $0.0024 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.

prefect-mcp-server AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prefect-mcp-server AGENTS.mdfortunto2/prefect-mcp-server	Instructions file	7	1y ago	MIT	A	593	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

prefect-mcp-server: Instructions file for Codex