What is mcpforge-cloud-workflow?

A workflow guide for authorized work in MCP Forge Cloud, including startup checks, GitHub delivery, and continuing an existing pull request. It also describes how to inspect the repository and handle local setup safely.

Use it to start Cloud work, verify the repository and prepared environment, make approved changes, and deliver or continue a GitHub pull request.

It reduces mistakes when working in an isolated checkout, especially around branches, existing changes, dependencies, and credentials. It also gives a consistent way to resume requested pull-request work.

How saagpatel/mcpforge configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to saagpatel/mcpforge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/saagpatel/mcpforge/main/.agents/skills/mcpforge-cloud-workflow/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/saagpatel/mcpforge

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/saagpatel/mcpforge/mcpforge-cloud-workflow/github.svg)](https://agentmods.dev/skills/saagpatel/mcpforge/mcpforge-cloud-workflow)

Your own site

<a href="https://agentmods.dev/skills/saagpatel/mcpforge/mcpforge-cloud-workflow"><img src="https://agentmods.dev/badge/skills/saagpatel/mcpforge/mcpforge-cloud-workflow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/saagpatel/mcpforge/mcpforge-cloud-workflow"><img src="https://agentmods.dev/badge/skills/saagpatel/mcpforge/mcpforge-cloud-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,127 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00033	$0.01127
Opus 5.5	$0.00013	$0.00451
Sonnet 5.5	$0.00007	$0.00225
Haiku 4.5	$0.00003	$0.00113

Measured 1mo ago against content hash 24220baa0a91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcpforge-cloud-workflow 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.

.agents/skills/mcpforge-cloud-workflow/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MCP Forge Cloud workflow

Use for authorized Cloud work or a requested PR follow-up in MCP Forge. Detect the Git root with git rev-parse --show-toplevel; run commands from that root. Read the nearest applicable AGENTS.md, supplied working instructions, and any referenced prepared-environment startup guide first.

Startup and scope

Inspect the repository identity, local branch, HEAD, and git status --short. Preserve unrelated changes, existing branches, and tracked manifests/locks. Use the existing isolated Cloud checkout; no extra worktree is needed by default.
Prepared startup permits authorized source edits and commits. Follow its cache variables and pinned Python argument for uv sync --check --locked --offline. Skip refresh if it passes. Only a stale local editable package permits the corresponding uv sync --locked --offline refresh, followed by a recheck. Investigate other mismatches; do not invent a fresh install, upgrade dependencies, or change locks to hide a startup problem.
Local tools, configuration, sign-ins, and credentials do not automatically transfer. Do not read credentials, .env files, keychains, OAuth stores, browser profiles, or raw private logs. Preserve network, privacy, approval, and secret settings.
Follow the current user's model preferences: GPT-6.1 Sol High for normal coding, coordination, and review; Medium for routine or clearly bounded work and helpers. Do not automatically escalate to Max, Extra High, or Ultra. Preferences do not configure the parent model picker, and helpers require supported native capabilities.

Continue the requested PR

Resolve the exact repository and PR through supported GitHub tools. Read its current open/closed/merged status, head repository/branch/commit, and base. Compare those with local HEAD/status before editing. Continue that branch only when open and consistent with the current authorization; do not create a duplicate PR or blindly continue a closed/merged PR. Follow-up scope does not imply merge authority.

Read the full file on GitHub · 98 lines

Changes

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 · 98 lines · 33 tokens per session scan A 24220baa0a91

Subscribe to this mod's changes

mcpforge-cloud-workflow is a skill published in the GitHub repository saagpatel/mcpforge (0 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 1,127 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-10-05.

Building agents Code Generation Commits Git and workflow Python ai-tools cli fastmcp mcp

mcpforge-cloud-workflow next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcpforge-cloud-workflowsaagpatel/mcpforge	Skill	0	3d ago	MIT	A	33	Claude Code, Codex
git-flowWrongStack/WrongStack	Skill	404	yesterday	MIT	A	110	Claude Code, Codex
git-flow-prsoulcodex/agentic	Skill	10	7d ago	MIT	A	103	Claude Code, Codex
commitnikolay-e/diffctx	Skill	6	yesterday	Apache-2.0	A	41	Claude Code
git-workflowprofclaw/profclaw	Skill	16	1mo ago	AGPL-3.0	A	19	Claude Code, Codex
git-advanced-workflowsHermeticOrmus/claude-code-game-development	Skill	78	1mo ago	MIT	A	54	Claude Code
diff-reviewwolfenazz/YzPzCode	Skill	20	yesterday	Apache-2.0	A	39	Claude Code, Codex

mcpforge: Skill for Claude Code