Borrowing it
Nothing to install: this file belongs to g-digital-by-Garrigues/MCP_Market_Distribution. 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/g-digital-by-Garrigues/MCP_Market_Distribution/main/.claude/commands/setup/setup-pipeline-repo.mdgit clone --depth 1 https://github.com/g-digital-by-Garrigues/MCP_Market_DistributionWrote 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/commands/g-digital-by-garrigues/mcp_market_distribution/setup-pipeline-repo)<a href="https://agentmods.dev/commands/g-digital-by-garrigues/mcp_market_distribution/setup-pipeline-repo"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/mcp_market_distribution/setup-pipeline-repo/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/commands/g-digital-by-garrigues/mcp_market_distribution/setup-pipeline-repo"><img src="https://agentmods.dev/badge/commands/g-digital-by-garrigues/mcp_market_distribution/setup-pipeline-repo.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.00026 | $0.01312 |
| Opus 5 | $0.00013 | $0.00656 |
| Sonnet 5 | $0.00005 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
Grade A, and why
setup-pipeline-repo 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 12d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-pipeline-repo — Bootstrap a new pipeline repo
You are bootstrapping a new GitHub repository to host the g-digital MCP distribution pipeline. The goal is to reduce per-MCP onboarding from ~1.5 hours of manual clicks to a guided ~5-minute flow.
Inputs
$1(required): GitHub org slug. For the canonical setup this isg-digital-by-Garrigues.$2(required): repository name (e.g.MCP_Market_Distributionor, for a throwaway test,MCP_Market_Distribution_setupskill_test).
You will also ask the engineer interactively for these three secret values (do not echo them back):
DOCKERHUB_USERNAME— Docker Hub org admin handle (typicallygdigital).DOCKERHUB_TOKEN— Docker Hub Organization Access Token with Read & Write to repos.BOT_PAT— GitHub Personal Access Token used by CI to commit release reports and push tags. If the dedicated bot account doesn't exist yet, the engineer's own PAT is acceptable as a temporary measure; record a TODO to rotate when the bot account lands.
Soft dependencies
This skill works in two modes; pick the highest-automation mode whose tooling is available:
- Full automation — the
ghCLI is installed ANDgh auth statusis green. Usegh apifor branch protection andgh secret setfor the three secrets. - Hybrid — only the GitHub MCP Server is available. Create the repo, LICENSE, README via MCP, then surface a copy-paste-friendly list of the manual steps the engineer still needs (URLs + values for each of the three secrets and the branch protection rule).
If neither is available, exit with a clear "install gh CLI or mount the GitHub MCP Server first" message — do NOT proceed.
Idempotency
Before changing anything, check whether the repo already exists (mcp__github__search_repositories or gh repo view). If it does AND it is correctly configured (LICENSE present, README present, three secrets configured, branch protection on main), emit a single "✅ already configured" line and exit 0.
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.
- 12d ago First seen · 92 lines · 26 tokens per session scan A 9b9cf15b6126
setup-pipeline-repo is a command published in the GitHub repository g-digital-by-Garrigues/MCP_Market_Distribution (0 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 1,312 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
ship
Deploy feature through automated staging validation to production with rollback testing.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
ci
Run CI validation, create PRs, and merge on green.