Iron Proxy Gateway logo

Iron Proxy Gateway

OrganizationPopular
nanocoai
iron-proxy-gateway

Use Iron Proxy for external accounts and APIs, including GitHub through gh. Connect credentials through the operator console and diagnose blocked requests without exposing tokens or adding unnecessary MCP servers.

Overview

Publishernanocoai
Repositorynanoclaw
Skill nameiron-proxy-gateway
Stars
30.9K
Forks
12.8K
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by nanocoai on GitHub. Read the source before you install it.

Installation

Install the Iron Proxy Gateway AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/nanocoai/nanoclaw.git /tmp/nanoclaw
mkdir -p .claude/skills
cp -r /tmp/nanoclaw/.claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway .claude/skills/iron-proxy-gateway
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Iron Proxy Gateway in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Iron Proxy Gateway on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Iron Proxy Gateway is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Iron Proxy gateway

Your outbound HTTP and HTTPS requests pass through your session's Iron Proxy. A policy-selected credential request waits for human approval before the proxy inserts a credential. You receive only a useless placeholder.

Policy failures

A bare 403 does not prove which layer rejected the request. It may be the destination rule, credential grant, human approval, or upstream API. Respect the block, report the hostname and observed error, and request a host-side check instead of guessing that credentials were never injected.

Connect an account

Run the shared command for the API hostname requested by the user:

bash
ncl groups connect --host <API hostname>

Return the exact connect_url and describe its action. An operator_console handoff requires the operator to configure the credential, grant, and destination in the gateway; it is not an OAuth link. Do not invent a connection flow when the result is unsupported. The command does not grant access or change policy.

Use the user's requested CLI or a direct HTTP client. Do not add an MCP server merely to connect an account. Clients requiring local authentication may use gateway-managed as a non-secret placeholder (for example GH_TOKEN for gh). Never use a real token in the client. Never run a local login to store credentials.

Request approval and account connection are separate. A 401 is not proof that injection did not happen: the stored token may itself be invalid. Report the observed result, follow the shared handoff, and verify with a credentialed request after the operator completes configuration. Never claim connected before success.

Rules

  • Never ask for, print, or store a raw API key or OAuth token.
  • Never bypass the configured proxy or its CA validation.
  • Never treat a pending approval as granted.
  • Never claim a blocked destination is connected.
  • Treat proxy errors as policy or operator-configuration errors, not as permission to weaken TLS.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Iron Proxy Gateway AI skill do?

Use Iron Proxy for external accounts and APIs, including GitHub through gh. Connect credentials through the operator console and diagnose blocked requests without exposing tokens or adding unnecessary MCP servers.

Why use Iron Proxy Gateway on TypingMind?

Because you install it once and use it with any model. Iron Proxy Gateway is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Iron Proxy Gateway in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-iron-proxy/payload/container/skills/iron-proxy-gateway. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Iron Proxy Gateway?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Iron Proxy Gateway?

As many as you like. As long as a model supports skills, you can use Iron Proxy Gateway with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Iron Proxy Gateway AI skill free?

Yes. It is published on GitHub by nanocoai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇