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 instructions/insforge/insforge-skills/agents-mdgit clone --depth 1 https://github.com/InsForge/insforge-skillsWrote 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/instructions/insforge/insforge-skills/agents-md)<a href="https://agentmods.dev/instructions/insforge/insforge-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/insforge/insforge-skills/agents-md.svg" alt="Measured on agentmods" 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 | $0.01125 | $0.01125 |
| Opus 5 | $0.00562 | $0.00562 |
| Sonnet 5 | $0.00225 | $0.00225 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
insforge-skills AGENTS.md 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidance
This document helps AI coding agents work effectively with the InsForge Agent Skills repository.
Repository Structure
agent-skills/
├── skills/
│ └── insforge/ # InsForge BaaS development skill
│ ├── SKILL.md # Skill manifest and overview
│ ├── database/ # Database operations
│ ├── auth/ # Authentication flows
│ ├── storage/ # File storage
│ ├── functions/ # Serverless functions
│ ├── ai/ # AI/ML operations
│ ├── realtime/ # Real-time messaging
│ ├── payments/ # Stripe and Razorpay app payment flows
│ └── email/ # Transactional email
│ └── insforge-cli/ # InsForge CLI project management
│ ├── SKILL.md # Skill manifest and command reference
│ └── references/ # CLI command reference
│ ├── database/ # Database migrations, query, RLS, vector, import/export
│ ├── auth.md
│ ├── create.md
│ ├── login.md
│ ├── functions-deploy.md
│ ├── payments/ # Shared payments routing plus provider references
│ │ ├── overview.md
│ │ ├── stripe.md
│ │ └── razorpay.md
│ ├── deployments/
│ │ ├── deploy.md
│ │ └── domains.md
│ └── ...
├── AGENTS.md # This file
├── CONTRIBUTING.md # Contribution guidelines
├── LICENSE # Apache License 2.0
└── README.md # Repository documentation
Skill Format
This repository follows the Agent Skills Open Standard.
SKILL.md Structure
Each skill contains a SKILL.md with:
- YAML Frontmatter: Required
nameanddescriptionfields, optionallicense. Nometadata:block — the OpenAI plugin submission portal rejects it; interface settings go in the skill'sagents/openai.yaml - Markdown Body: Instructions, examples, and references to module documentation
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.
- 3d ago First seen · 107 lines · 1,125 tokens per session scan A 19076a8fe1a7
insforge-skills AGENTS.md is an instructions file published in the GitHub repository InsForge/insforge-skills (36 stars, last pushed 5d ago), licensed Apache-2.0. It adds 1,125 tokens to every session, about $0.0056 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.