mongez-agent-kit-agent-integrations

mongez-agent-kit-agent-integrations is a skill for Claude Code, Codex from hassanzohdy/agent-kit. It costs 86 tokens per session (3,404 once invoked), scanned A, original, MIT.

A set of setup instructions for connecting agent-kit to coding agents such as Claude Code, Cursor, Codex, Gemini CLI, and GitHub Copilot. It shows which files each agent reads and which command options to use.

In plain words
What is it for?
Use it to initialize AGENTS.md, generate agent-specific instruction files, choose supported targets, and configure each listed coding agent.
Why use it?
Different coding agents expect instructions in different files and may need different reload steps, making shared project guidance tedious to configure.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hassanzohdy/agent-kit/agent-integrations
Any agent
npx skills add hassanzohdy/agent-kit --skill agent-integrations
Clone the repo
git clone --depth 1 https://github.com/hassanzohdy/agent-kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mongez-agent-kit-agent-integrations

README.md
[![agentmods](https://agentmods.dev/badge/skills/hassanzohdy/agent-kit/agent-integrations.svg)](https://agentmods.dev/skills/hassanzohdy/agent-kit/agent-integrations)
Your own site
<a href="https://agentmods.dev/skills/hassanzohdy/agent-kit/agent-integrations"><img src="https://agentmods.dev/badge/skills/hassanzohdy/agent-kit/agent-integrations.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,404 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00086 $0.03404
Opus 5 $0.00043 $0.01702
Sonnet 5 $0.00017 $0.00681
Haiku 4.5 $0.00009 $0.00340

Measured 3d ago against content hash b6fb0f6a5b0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mongez-agent-kit-agent-integrations 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.

skills/agent-integrations/SKILL.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent integrations

You're a developer who wants their AI coding agent to read the same project conventions as the rest of the team and pick up the skills bundled inside the npm packages you depend on. This page is the per-IDE cookbook. Pick your agent below, copy-paste the snippet, ship.

Every section follows the same three-step pattern — what differs is which files agent-kit writes, which --target flag to pass, and what reload step the agent needs.

The shared baseline

Before any per-IDE step, every project does the same bootstrap — no install needed:

npx @mongez/agent-kit@latest init

That runs the latest published agent-kit on the fly (use the scoped name with npx; npx agent-kit … unscoped resolves a different package) and writes a starter AGENTS.md at the project root (only if one doesn't already exist), then derives CLAUDE.md, .gemini/GEMINI.md, .github/copilot-instructions.md, and CONVENTIONS.md from it. It also seeds agentKit.targets in package.json["claude"] by default, or pass --target claude,cursor,… to choose — so the otherwise-implicit default is visible and editable. (init is one-time, so always-latest npx is ideal; the recurring sync belongs as a pinned dev dependency.) From here, the per-agent sections below differ only in which --target you pass and which directory the skills land in.

Then wire sync into postinstall so every future yarn install / npm install keeps everything current:

{
  "scripts": {
    "postinstall": "agent-kit sync"
  }
}

init can wire this for you. When @mongez/agent-kit is already a dependency/devDependency and no postinstall exists yet, init writes the script above automatically. The zero-install npx @mongez/agent-kit@latest init bootstrap can't (nothing is in node_modules to run it), so add it by hand after installing agent-kit — init prints a reminder.

At-a-glance: every supported agent

A one-table lookup before you scroll into the per-agent sections. Two things to watch for in the Skills folder column — the singular/plural variants are real and easy to mis-type:

Read the full file on GitHub · 295 lines

Changes

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.

  1. 3d ago First seen · 295 lines · 86 tokens per session scan A b6fb0f6a5b0e

Subscribe to this mod's changes

mongez-agent-kit-agent-integrations is a skill published in the GitHub repository hassanzohdy/agent-kit (2 stars, last pushed 17d ago), licensed MIT. It adds 86 tokens to every session and 3,404 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens