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.
git clone --depth 1 https://github.com/os-tack/fcpWrote 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/plugins/os-tack/fcp/marketplace)<a href="https://agentmods.dev/plugins/os-tack/fcp/marketplace"><img src="https://agentmods.dev/badge/plugins/os-tack/fcp/marketplace/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/plugins/os-tack/fcp/marketplace"><img src="https://agentmods.dev/badge/plugins/os-tack/fcp/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fcp-plugins marketplace 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "fcp-plugins",
"owner": {
"name": "Scott Meyer"
},
"metadata": {
"description": "FCP plugin marketplace \u2014 MCP servers for complex file formats, Python/Rust codebases, regex construction, and PDF documents",
"version": "0.2.26"
},
"plugins": [
{
"name": "fcp",
"source": "./",
"description": "All FCP servers \u2014 diagrams, infrastructure, music, spreadsheets, presentations, PDF documents, Python/Rust codebases, and regex construction",
"version": "0.2.26",
"license": "MIT",
"category": "development",
"keywords": [
"fcp",
"mcp",
"drawio",
"terraform",
"midi",
"sheets",
"slides",
"pdf",
"python",
"rust",
"regex"
]
},
{
"name": "fcp-drawio",
"source": {
"source": "github",
"repo": "os-tack/fcp-drawio"
},
"description": "Create and edit draw.io diagrams through intent-level commands",
"version": "0.3.0",
"license": "MIT",
"category": "development",
"keywords": [
"drawio",
"diagrams",
"architecture",
"mcp"
]
},
{
"name": "fcp-terraform",
"source": {
"source": "github",
"repo": "os-tack/fcp-terraform"
},
"description": "Generate Terraform HCL through resource declarations",
"version": "0.2.0",
"license": "MIT",
"category": "devops",
"keywords": [
"terraform",
"hcl",
"infrastructure",
"mcp"
]
},
{
"name": "fcp-midi",
"source": {
"source": "github",
"repo": "os-tack/fcp-midi"
},
"description": "Semantic MIDI music composition",
"version": "0.2.0",
"license": "MIT",
"category": "creative",
"keywords": [
"midi",
"music",
"composition",
"mcp"
]
},
{
"name": "fcp-sThe plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 190 lines scan A e1dc01b11ea7
fcp-plugins marketplace is a plugin published in the GitHub repository os-tack/fcp (2 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
umt
28 production-ready MCP servers for coding agents — filesystem, GitHub, npm, research, and more. Ships zero-config servers out of the box and the umt CLI to connect any harness.
rashomon
Evaluate prompts and skills through parallel execution comparison in git worktrees. Prompt optimization with BP-001009 patterns, skill creation/update with quality grading, and blind A/B evaluation.
interview-me
Deep-dive spec interviewer that produces production-grade specs through rigorous 1-on-1 interviews, with --verify drift detection against the codebase.
synapsor
Turn one application data change into a disabled, reviewable Synapsor Safe Action without giving the Cursor agent SQL or commit authority.
airport-lounge-list
Search 8,500+ airport lounges worldwide and check which ones your credit card, membership, airline status or ticket class gets you into. Hosted remote MCP server, no install and no API key.
sanction
Independent authorization plane for AI agents — approve, escalate, or deny spend, tools, credentials, and provisioning. Wires the hosted wallet MCP; the host must ask before acting.