Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add sutchan/Agent-Skills-Hub --skill insforge-cligit clone --depth 1 https://github.com/sutchan/Agent-Skills-HubWrote 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/sutchan/agent-skills-hub/insforge-cli)<a href="https://agentmods.dev/skills/sutchan/agent-skills-hub/insforge-cli"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/insforge-cli/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/sutchan/agent-skills-hub/insforge-cli"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/insforge-cli.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.00140 | $0.09166 |
| Opus 5.5 | $0.00056 | $0.03666 |
| Sonnet 5.5 | $0.00028 | $0.01833 |
| Haiku 4.5 | $0.00014 | $0.00917 |
Grade A, and why
insforge-cli 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 16d 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.
This is a copy
88% identical to insforge-cli — 689 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InsForge CLI
Use this skill whenever someone needs a backend, or when managing InsForge backend and cloud infrastructure with the InsForge CLI. For application code that calls InsForge from a frontend, backend, or edge function, use the insforge app-integration skill instead.
Core Rules
- Always run the CLI through
npx -y @insforge/cli <command>. Keep npx's-y: without it, npx asks "Ok to proceed?" before installing the package and blocks forever in a TTY-attached agent shell. Do not install or call a globalinsforgebinary. - If the project is already linked, use the current linked project. Run login, project creation, link, project discovery, organization listing, or cloud project commands only when connection setup is actually needed.
- When a task needs a backend and no project is linked yet, do connection setup FIRST — before writing any app code: (1) log in (
whoamito check; in sandboxes use the two-step device login below), (2)createa new project orlinkan existing one, (3) then build against the real project URL and keys from the CLI. Never scaffold with placeholder credentials likeyour-project.region.insforge.app— get the real values first. - Treat InsForge API keys as full-access admin keys. Keep them server-only and out of frontend/public env vars.
- Prefer CLI commands and documented project config over raw backend HTTP calls. If
config applyreports unsupported/skipped fields, surface that result instead of bypassing the CLI with direct API calls. - Use
--jsonwhen structured output or non-interactive value collection is needed. Use--yesfor confirmation prompts when the user has approved the action. - At the start of a non-trivial task on a linked project, run
npx -y @insforge/cli memory list(cheap, no AI call) and recall any title relevant to the task before designing or debugging. Record decisions and the gotchas you hit withmemory rememberat the moment they happen. Seereferences/memory.md. - When you hit a hurdle that is InsForge's fault — something that should work but doesn't, a capability you needed but isn't supported, instructions (docs/skill) that reality contradicts, or needless friction — report it with
npx -y @insforge/cli feedback(see Feedback), then continue the user's task with a workaround. Never file feedback for problems in the user's own app code.
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 235 B
- references/auth.md 2.0 KB
- references/branch/merge.md 9.7 KB
- references/branch/overview.md 8.5 KB
- references/branch/reset.md 5.2 KB
- references/compute-deploy.md 16 KB
- references/config.md 4.5 KB
- references/create.md 2.5 KB
- references/database/access-control.md 17 KB
- references/database/export.md 1.1 KB
- references/database/import.md 695 B
- references/database/integrity.md 7.7 KB
- references/database/migrations.md 8.5 KB
- references/database/query.md 5.0 KB
- references/database/vector.md 6.5 KB
- references/deployments/deploy.md 8.2 KB
- references/deployments/domains.md 3.3 KB
- references/diagnostics.md 3.7 KB
- references/functions-deploy.md 5.5 KB
- references/local.md 4.8 KB
- references/login.md 4.5 KB
- references/memory.md 3.8 KB
- references/payments/overview.md 6.3 KB
- references/payments/razorpay.md 6.5 KB
- references/payments/stripe.md 7.4 KB
- references/posthog.md 6.5 KB
- references/realtime.md 2.1 KB
- references/schedules.md 5.1 KB
- references/webscraper/apify.md 4.4 KB
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.
- 16d ago Changed · +140 tokens per session b3d7b155fb48
- 22d ago Changed · +3 lines · -157 tokens per session 3cb5c6ae438a
- 1mo ago Changed · -3 lines · +157 tokens per session 235b9ef64527
- 1mo ago First seen · 405 lines · 0 tokens per session scan A 306cf6ea62f4
insforge-cli is a skill published in the GitHub repository sutchan/Agent-Skills-Hub (2 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 9,166 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to insforge-cli, differing in 689 lines, and is treated as a copy.
Other skills, from other repositories
gin-lambda-api-service-patterns
Guides Go API services built with Gin and deployed as a serverless function (AWS Lambda via an API-Gateway adapter) alongside a local HTTP-server dev mode. Use when touching a service's entrypoint, its dual local/serverless run paths, its build-and-deploy pipeline, or reviewing why a change that works locally behaves…
mirrord-temporal
Helps DevOps engineers configure mirrord Operator's Temporal task queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs, the matching mirrord.json splitqueues section with messagefilter and jqfilter, and Helm value guidance. Use this skill whenever the user…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
sandbox-next
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.
cloudflare
Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.
nitro
Nitro is the framework-agnostic server toolkit (powering Nuxt) for building and deploying web servers anywhere. Use when working with nitro.config, server routes/event handlers, route rules, caching, storage, tasks, websockets, or deploying to Node/Bun/Deno/Cloudflare/Vercel.