Name: clone-space-mcp
Author: xenodeve

Imported from xenodeve/clone-space-mcp (AGENTS.md). Install upstream with npx skills add xenodeve/clone-space-mcp. Copyright stays with the author.

AGENTS.md

This repo's operating manual is CLAUDE.md — read it first, regardless of which agent you are. It carries the north-star, repo layout, commands, the session-start read protocol, and what is mechanically enforced.

Two things that bind you even though the Claude Code hooks do not:

pre-push guards. .githooks/ re-checks that every push carries a GitHub issue reference and blocks a large dirty tree or committed build artifacts. Opt in once per clone: git config core.hooksPath .githooks.
Branch ruleset. Direct pushes to main are blocked — everything arrives through a PR — and unresolved review threads block merge. CI required checks are not active yet: GitHub Actions is locked on this account for billing, so lint/typecheck/test/build never report and were deliberately kept out of the ruleset rather than deadlocking every PR (issue #2). Until that closes, a merge performed on the web is not gated by anything.

The ship gate is bun run verify.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install clone-space-mcp and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "xenodeve-clone-space-mcp-clone-space-mcp", "kind": "skill", "name": "clone-space-mcp", "description": "This repo's operating manual is **[`CLAUDE.md`](CLAUDE.md)** — read it first, regardless of which agent you are. It carries the north-star, repo layout, commands, the session-start read protocol, and what is mechanically enforced.", "publisher": "xenodeve", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "This repo's operating manual is **[`CLAUDE.md`](CLAUDE.md)** — read it first, regardless of which agent you are. It carries the north-star, repo layout, commands, the session-start read protocol, and what is mechanically enforced." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/xenodeve/clone-space-mcp", "path": "AGENTS.md", "ref": "205a616cc318a4857da0b117c1b88a82933680d4", "url": "https://github.com/xenodeve/clone-space-mcp/blob/205a616cc318a4857da0b117c1b88a82933680d4/AGENTS.md", "key": "xenodeve/clone-space-mcp/AGENTS.md" } }, "instructions": "# AGENTS.md\n\nThis repo's operating manual is **[`CLAUDE.md`](CLAUDE.md)** — read it first, regardless of which\nagent you are. It carries the north-star, repo layout, commands, the session-start read protocol,\nand what is mechanically enforced.\n\nTwo things that bind you even though the Claude Code hooks do not:\n\n- **`pre-push` guards.** `.githooks/` re-checks that every push carries a GitHub issue reference\n and blocks a large dirty tree or committed build artifacts. Opt in once per clone:\n `git config core.hooksPath .githooks`.\n- **Branch ruleset.** Direct pushes to `main` are blocked — ever", "cost": { "context_tokens": 257 } }

clone-space-mcp

About

AGENTS.md

Use it

Install clone-space-mcp and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews