compat-fixture
v0.1.0Not a runnable agent: a plugin-compat gate fixture that carries all six Curie authoring extensions (systemPrompt, starterPrompts, secrets, triggers, approvalPolicy, toolPolicy) so `claude plugin validate` exercises the warn-and-ignore degradation contract for every one of them (#538). A dedicated fixture keeps these fields off the real example bundles, where approvalPolicy and systemPrompt would change runtime behavior for no functional benefit. Its toolPolicy is NOT an adoption example: the patterns use wildcard server segments only (the fixture declares no MCP servers and no connectors.yaml), and no runtime enforces a toolPolicy yet.
By CurieTech35 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 0 skill or MCP entries
- Source updated
- Aug 30, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install compat-fixture for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install compat-fixture@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/curie-eng/curieClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is examples/compat-fixture/.
Plugin files
└── .claude-plugin/plugin.json
Plugin manifests1
{
"name": "compat-fixture",
"version": "0.1.0",
"description": "Not a runnable agent: a plugin-compat gate fixture that carries all six Curie authoring extensions (systemPrompt, starterPrompts, secrets, triggers, approvalPolicy, toolPolicy) so `claude plugin validate` exercises the warn-and-ignore degradation contract for every one of them (#538). A dedicated fixture keeps these fields off the real example bundles, where approvalPolicy and systemPrompt would change runtime behavior for no functional benefit. Its toolPolicy is NOT an adoption example: the patterns use wildcard server segments only (the fixture declares no MCP servers and no connectors.yaml), and no runtime enforces a toolPolicy yet.",
"author": {
"name": "CurieTech"
},
"keywords": [
"fixture",
"plugin-compat",
"extensions"
],
"systemPrompt": "You are a compatibility fixture; you are never actually run.",
"starterPrompts": [
"This bundle exists only to exercise the plugin-compat gate."
],
"secrets": [
"FIXTURE_CONNECTOR_TOKEN"
],
"triggers": [
{
"type": "cron",
"schedule": "0 9 * * 1"
},
{
"type": "webhook",
"path": "fixture-hook"
}
],
"approvalPolicy": {
"gates": [
{
"gate": "Bash",
"route": "fixture-route"
}
]
},
"toolPolicy": {
"enforcement": "curie/mcp-tool-policy@1",
"allow": [
"*/search_*"
],
"approvalRequired": [
"*/pods_*"
],
"deny": [
"*/resources_create_or_update"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[compat-fixture on Agent Plugins Marketplace](https://pluginsmp.com/plugins/compat-fixture)