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 agentmods add skills/insforge/insforge-skills/insforge-clinpx skills add InsForge/insforge-skills --skill insforge-cligit clone --depth 1 https://github.com/InsForge/insforge-skillsWhat 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 | $0.00157 | $0.09002 |
| Opus 5 | $0.00078 | $0.04501 |
| Sonnet 5 | $0.00031 | $0.01800 |
| Haiku 4.5 | $0.00016 | $0.00900 |
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 2d 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 — 682 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 — 402 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.
- 2d ago First seen · 402 lines · 157 tokens per session scan A 235b9ef64527
insforge-cli is a skill published in the GitHub repository InsForge/insforge-skills (36 stars, last pushed 4d ago), licensed Apache-2.0. It adds 157 tokens to every session and 9,002 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to insforge-cli, differing in 682 lines, and is treated as a copy.
Other skills, from other repositories
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…