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/troubleshootingnpx skills add hassanzohdy/agent-kit --skill troubleshootinggit 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/troubleshooting)<a href="https://agentmods.dev/skills/hassanzohdy/agent-kit/troubleshooting"><img src="https://agentmods.dev/badge/skills/hassanzohdy/agent-kit/troubleshooting.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.00128 | $0.02009 |
| Opus 5 | $0.00064 | $0.01005 |
| Sonnet 5 | $0.00026 | $0.00402 |
| Haiku 4.5 | $0.00013 | $0.00201 |
Grade A, and why
mongez-agent-kit-troubleshooting 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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting
Symptom → cause → fix. Find the line that matches what you hit.
Auto-trigger: user reports any error/log line from
agent-kit init,agent-kit sync, oragent-kit watch; user says "command not found", "skills not showing up", "wrong package", "pick matched no installed packages", "collision", "AGENTS.md missing", "my skill folder disappeared"; user asks "why doesn't X work" after running an agent-kit command.Skip when: the question is about how to use a feature (CLI usage, configuration, monorepos) rather than a malfunction.
agent-kit: command not found
Symptom. postinstall: agent-kit sync runs but errors with command not found, or you typed agent-kit sync in a terminal and got the same.
Cause. The bare agent-kit binary only resolves when @mongez/agent-kit is installed locally (in the project's node_modules/.bin). The zero-install npx @mongez/agent-kit@latest init bootstrap installs nothing.
Fix. Install agent-kit as a dev dependency:
npm install -D @mongez/agent-kit
# or: yarn add -D @mongez/agent-kit / pnpm add -D @mongez/agent-kit
Now postinstall: agent-kit sync and any plain agent-kit sync invocation will resolve the local binary.
npx agent-kit … is fetching the wrong package
Symptom. npx agent-kit init (or sync) downloads and runs something unrecognizable — different help text, unfamiliar flags.
Cause. Without the scope, agent-kit resolves to a different, unrelated npm package when nothing is installed locally. npm doesn't fall back to scoped names.
Fix. Use the scoped name when running without a local install:
npx @mongez/agent-kit@latest init
After installing agent-kit as a dev dep, the unscoped npx agent-kit … is fine — npx prefers the local binary in node_modules/.bin.
Sync said it succeeded but my agent shows zero skills
Symptom. .claude/skills/ (or .cursor/skills/, .codex/skills/, …) exists and contains the expected folders, but the agent UI shows no skills.
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.
- 5d ago First seen · 151 lines · 128 tokens per session scan A cf083e139716
mongez-agent-kit-troubleshooting is a skill published in the GitHub repository hassanzohdy/agent-kit (2 stars, last pushed 18d ago), licensed MIT. It adds 128 tokens to every session and 2,009 once invoked, about $0.0006 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…