FastMCP is a Python framework for building Model Context Protocol applications, which connect language models with tools and data through servers and clients. Developers use it to expose Python functions as tools, connect to local or remote MCP servers, and build interactive tool interfaces. The catalogue includes eight skills, three instructions, two rules, one setting, and one hook for FastMCP.
Borrowing it
Nothing to install: this file belongs to PrefectHQ/fastmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PrefectHQ/fastmcp/main/.agents/skills/fix-issue/SKILL.mdgit clone --depth 1 https://github.com/PrefectHQ/fastmcpWrote 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/skills/prefecthq/fastmcp/fix-issue)<a href="https://agentmods.dev/skills/prefecthq/fastmcp/fix-issue"><img src="https://agentmods.dev/badge/skills/prefecthq/fastmcp/fix-issue/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.
<a href="https://agentmods.dev/skills/prefecthq/fastmcp/fix-issue"><img src="https://agentmods.dev/badge/skills/prefecthq/fastmcp/fix-issue.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00630 |
| Opus 5.5 | $0.00012 | $0.00252 |
| Sonnet 5.5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
fix-issue 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 1mo 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix a selected issue
Read AGENTS.md and the contribution policy in the development guide. Read the issue's full discussion, relevant history, and associated PRs in all states. Evaluate existing contributions before writing a competing fix; use review-issue when assignment is the next decision. Preserve contributor authorship when carrying existing work forward.
Establish the contract
Trace the public request to the failing operation. Confirm supported behavior is broken, not merely surprising. State the scope and compatibility boundary before implementation: which inputs must change, which adjacent behavior must remain, and any migration needed. If the intended contract is unresolved, bring that precise question to the maintainer.
Red, green, review
Use python-tests. Reproduce the failure on unchanged code, confirm it fails for the right reason, then make the smallest causal fix. Test explicit overrides and neighboring supported paths that share the changed branch. Avoid expanding the fix to unrelated standards gaps.
Self-review the full change with review-pr, including docs and dependency bounds. Separate necessary compatibility changes from accidental regressions and say whether a breaking change remains. Do not infer compatibility from passing tests.
Run the repository's required dependency sync, full tests, and static checks before committing. Honor branch and attribution conventions. If a required check fails, investigate and report evidence rather than hiding the failure.
Publish and follow through
Within existing authorization, update the existing PR or open a focused one, using draft status when appropriate. Follow repository PR-body conventions and the user's pr-body skill when available. Describe the actual user-visible change and any migration, not the development diary.
For a maintainer implementation of a community issue, apply Contributor credit before committing and publishing. Read the issue author's GitHub profile to establish their account identity; prefer the GitHub-provided noreply address, and ask if identity is unclear. Add their Co-authored-by: Name <email> trailer to the implementation commit and at the end of the PR description, alongside existing contributor attribution. Reporting the problem is enough; do not require code or root-cause analysis. Honor opt-outs and do not credit bot accounts as human issue contributors.
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.
- 1mo ago Changed · +4 lines 9e34f30bbd9d
- 1mo ago Changed a9954862af6e
- 1mo ago First seen · 27 lines · 29 tokens per session scan A c9911f4bb1a1
fix-issue is a skill published in the GitHub repository PrefectHQ/fastmcp (28,322 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 630 once invoked, about $0.0001 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-09-12.
fix-issue compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| fix-issuePrefectHQ/fastmcp | Skill | 28k | today | Apache-2.0 | A | 29 | Claude Code, Codex |
| recorded-testsNVIDIA-NeMo/Guardrails | Skill | 7.4k | yesterday | none | A | 125 | Claude Code, Codex |
| iterate-implementationhumanlayer/humanlayer | Skill | 13k | yesterday | Apache-2.0 | A | 16 | Claude Code, Codex |
| verify-omnigentomnigent-ai/omnigent | Skill | 11k | today | Apache-2.0 | A | 100 | Claude Code, Codex |
| typescript-testingComposioHQ/composio | Skill | 31k | yesterday | MIT | A | 92 | Claude Code, Codex |
| cli-e2eComposioHQ/composio | Skill | 31k | yesterday | MIT | A | 62 | Claude Code, Codex |
| ios-simulatorcallstack/agent-device | Skill | 5.3k | yesterday | MIT | A | 69 | Claude Code, Codex |