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/overviewnpx skills add hassanzohdy/agent-kit --skill overviewgit clone --depth 1 https://github.com/hassanzohdy/agent-kitWrote 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/hassanzohdy/agent-kit/overview)<a href="https://agentmods.dev/skills/hassanzohdy/agent-kit/overview"><img src="https://agentmods.dev/badge/skills/hassanzohdy/agent-kit/overview.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.00087 | $0.03615 |
| Opus 5 | $0.00044 | $0.01808 |
| Sonnet 5 | $0.00017 | $0.00723 |
| Haiku 4.5 | $0.00009 | $0.00362 |
Grade A, and why
mongez-agent-kit-overview 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 4d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Kit
If you're working with AI coding agents — Claude Code, Cursor, Copilot, Codex, Aider, Gemini CLI — you've probably noticed two annoying chores. First, every agent reads its own project-instructions file from its own path, so the same content ends up copy-pasted across CLAUDE.md, .gemini/GEMINI.md, .github/copilot-instructions.md, and a half-dozen others. Second, your team's hard-won prompt patterns and skill files live in repos that downstream consumers can't reach — so everyone reinvents them.
agent-kit is a small CLI (and library) that solves both. Write your project instructions once in AGENTS.md — the emerging open standard read natively by Codex, Cursor, Amp, Jules, Factory, Windsurf, OpenCode, and others — and let agent-kit derive the agent-specific files. Ship your skills from any npm package and let agent-kit sync discover and mirror them into every agent's skills directory, with collision-free folder names.
Highlighted features
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.
- 4d ago First seen · 173 lines · 87 tokens per session scan A ceee91933a17
mongez-agent-kit-overview is a skill published in the GitHub repository hassanzohdy/agent-kit (2 stars, last pushed 17d ago), licensed MIT. It adds 87 tokens to every session and 3,615 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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…