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.
npx agentmods add instructions/fortunto2/prefect-mcp-server/agents-mdgit clone --depth 1 https://github.com/fortunto2/prefect-mcp-serverWrote 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.
[](https://agentmods.dev/instructions/fortunto2/prefect-mcp-server/agents-md)<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="Measured on agentmods" height="20"></a>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 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00059 | $0.00059 |
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 5d 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.
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.pyexposes all MCP tools and the console entry point defined inpyproject.toml.docs/prefect_mcp_documentation.mdcaptures user-facing behavior; update it alongside feature changes.Makefile,pyproject.toml, anduv.lockmanage builds and dependencies; never edituv.lockby hand.dist/is generated output from packaging; remove artifacts withmake cleanbefore committing.
Build, Test, and Development Commands
make build(wrapsuv build) packages the project for distribution and refreshesdist/.make testrunspytest; use it before every push even if no dedicated tests exist yet.uv run prefect-mcp-server --helpexercises the CLI entry point locally. ProvidePREFECT_API_URLandPREFECT_API_KEYin your shell when hitting a live Prefect instance.make cleanclears 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_casefor functions/tools (get_flow_by_id) andSCREAMING_SNAKE_CASEfor 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_pkgif 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.asynciofor 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.
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.
- 5d ago First seen · 36 lines · 593 tokens per session scan A 9fb58c57af73
prefect-mcp-server AGENTS.md is an instructions file published in the GitHub repository fortunto2/prefect-mcp-server (7 stars, last pushed 11mo ago), licensed MIT. It adds 593 tokens to every session, about $0.0030 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.
Other instructions, from other repositories
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.
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).
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.
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.
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.
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).