Borrowing it
Nothing to install: this file belongs to onionuser79/Open-PR-DIGI-MCP-Server-for-Claude-AI. 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/onionuser79/Open-PR-DIGI-MCP-Server-for-Claude-AI/main/.claude/skills/setup-remote-access/SKILL.mdgit clone --depth 1 https://github.com/onionuser79/Open-PR-DIGI-MCP-Server-for-Claude-AIWrote 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/skills/onionuser79/open-pr-digi-mcp-server-for-claude-ai/setup-remote-access)<a href="https://agentmods.dev/skills/onionuser79/open-pr-digi-mcp-server-for-claude-ai/setup-remote-access"><img src="https://agentmods.dev/badge/skills/onionuser79/open-pr-digi-mcp-server-for-claude-ai/setup-remote-access/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/skills/onionuser79/open-pr-digi-mcp-server-for-claude-ai/setup-remote-access"><img src="https://agentmods.dev/badge/skills/onionuser79/open-pr-digi-mcp-server-for-claude-ai/setup-remote-access.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.00070 | $0.01071 |
| Opus 5 | $0.00035 | $0.00535 |
| Sonnet 5 | $0.00014 | $0.00214 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
setup-remote-access scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8080/mcp # expect 401 How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure remote access + bearer-token auth
Drive the operator through enabling pr-digi-mcp serve-http (MCP over Streamable
HTTP, gated by a bearer token). Full reference: docs/remote-access.md.
Secret hygiene — non-negotiable. The bearer token must NOT land in this chat, in
nodes.yaml, or in the repo. Have the operator generate and store it themselves using the!shell prefix (so the value stays in their terminal). Never run a command that prints the token into the conversation, and never ask the operator to paste it to you.
1. Establish the deployment shape (ask first)
- Local only (client on the same host, or you'll add a tunnel/proxy later) →
bind loopback
127.0.0.1(default). No TLS needed on the MCP itself. - Remote, direct TLS → bind a reachable host with
--tls-cert/--tls-key. - Remote, behind a reverse proxy (nginx/caddy/traefik terminates TLS) → keep
--host 127.0.0.1and proxy to it.
serve-http refuses a non-loopback bind without TLS unless --insecure is
passed — steer away from --insecure except for a throwaway local test.
2. Generate + store the token (operator runs; secret stays out of chat)
Have the operator run, via !:
! python3 -c "import secrets; print(secrets.token_urlsafe(32))"
Then store it — keyring preferred (paste at the prompt; multiple comma-separated for several operators / rotation):
! keyring set pr-digi-mcp http_tokens
…or, for an env-based setup, add to their shell profile (not committed):
export PR_DIGI_MCP_HTTP_TOKENS="<token>[,<token2>...]"
You (Claude) don't need the value — only confirm it's stored.
3. Start the server
Pick the flags for the shape from step 1, e.g.:
pr-digi-mcp serve-http --host 127.0.0.1 --port 8080 # local / behind proxy
pr-digi-mcp serve-http --host 0.0.0.0 --port 8080 --tls-cert cert.pem --tls-key key.pem # direct TLS
For a persistent service, suggest a systemd unit (Linux) or launchd agent (macOS)
that sets the token env / uses the keyring and runs serve-http — offer to draft
one if wanted. It won't start without a token configured.
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.
- 10d ago First seen · 87 lines · 70 tokens per session scan A 31f71639fc66
setup-remote-access is a skill published in the GitHub repository onionuser79/Open-PR-DIGI-MCP-Server-for-Claude-AI (0 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,071 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…