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/hassanzohdy/agent-kit/cli-usagenpx skills add hassanzohdy/agent-kit --skill cli-usagegit clone --depth 1 https://github.com/hassanzohdy/agent-kitWhat 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.00040 | $0.01866 |
| Opus 5 | $0.00020 | $0.00933 |
| Sonnet 5 | $0.00008 | $0.00373 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
mongez-agent-kit-cli-usage 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 yesterday.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-kit CLI usage
Three commands. All are idempotent — running them twice in a row is a no-op the second time.
agent-kit init
Scaffold a starter AGENTS.md (only if it does not exist), derive the per-tool files from it, and seed agentKit.targets in package.json.
npx @mongez/agent-kit@latest init # no install — runs the latest published version
npx @mongez/agent-kit@latest init --target claude,cursor
Scoped name with
npx. Usenpx @mongez/agent-kit …(scoped) when running without a local install —npx agent-kit …(unscoped) resolves a different package. The bareagent-kitbinary only works once it's installed locally.
Flags:
--cwd <path>— start from a different working directory (defaults toprocess.cwd()).--target <names>— comma-separated skill targets to write intopackage.json'sagentKit.targets(claude,copilot,cursor,codex,opencode,amp,goose,kiro,antigravity). Defaults toclaude. Passing this overwrites an existingagentKit.targets; without it, an already-set value is left alone. Unknown names error out before anything is written.
init vs sync — different delivery
initis a one-time scaffold →npx @mongez/agent-kit@latest initis ideal (zero install, always latest).syncruns on every install and in CI → install agent-kit as a pinned dev dependency and call it frompostinstall. Don't route the recurring sync through always-latestnpx— a new agent-kit version could silently change generated output, breaking build reproducibility. Ad-hoc manualnpx @mongez/agent-kit@latest syncis fine.
Behavior:
- If
AGENTS.mdexists → leave it alone. - If
AGENTS.mdis missing → write a starter template. - Always derives
CLAUDE.md,.gemini/GEMINI.md,.github/copilot-instructions.md,CONVENTIONS.md. - Seeds
agentKit.targetsintopackage.json: writes["claude"](the built-in default, made explicit so it's discoverable and editable) when noagentKit.targetsexists; writes--target's value when that flag is passed, overwriting any existing list. An existingagentKitblock's other fields (pick,omit, …) and the file's indentation are preserved. Notetargetsonly gates the skills export —inititself doesn't sync skills, so the seeded value first takes effect on the nextagent-kit sync. - Wires
"postinstall": "agent-kit sync"intopackage.json— but only when it's safe: (1)@mongez/agent-kitis already a declareddependency/devDependency(so the bareagent-kitbinary resolves at install time — thenpx @mongez/agent-kit@latest initbootstrap installs nothing, so wiring a postinstall there would break the next install), and (2) nopostinstallalready exists (an existing one is never clobbered). When either gate blocks,initprints a hint instead of writing.
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.
- yesterday First seen · 131 lines · 40 tokens per session scan A 9dce42593cb6
mongez-agent-kit-cli-usage is a skill published in the GitHub repository hassanzohdy/agent-kit (2 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 1,866 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.