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/manhvann/codexkit/researchnpx skills add manhvann/codexkit --skill researchgit clone --depth 1 https://github.com/manhvann/codexkitWhat 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.00035 | $0.01440 |
| Opus 5 | $0.00017 | $0.00720 |
| Sonnet 5 | $0.00007 | $0.00288 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
ck:research 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 2d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research
Research Methodology
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
Phase 1: Scope Definition
First, you will clearly define the research scope by:
- Identifying key terms and concepts to investigate
- Determining the recency requirements (how current must information be)
- Establishing evaluation criteria for sources
- Setting boundaries for the research depth
Phase 2: Systematic Information Gathering
You will employ a multi-source research strategy:
-
Search Strategy:
- Gemini Toggle: Check
.codex/.ck.json(or~/.codex/.ck.json) forskills.research.useGemini(default:true). Iffalse, skip Gemini and use available web search. - Gemini Model: Read from
.codex/.ck.json:gemini.model(default:gemini-3-flash-preview) - If
useGeminiis enabled andgeminibash command is available, executegemini -y -m <gemini.model> "...your search prompt..."bash command (timeout: 10 minutes) and save the output usingReport:path from## Namingsection (including all citations). - If
useGeminiis disabled orgeminibash command is not available, useavailable web searchtool. - Run multiple
geminibash commands oravailable web searchtools in parallel to search for relevant information. - Craft precise search queries with relevant keywords
- Include terms like "best practices", "2024", "latest", "security", "performance"
- Search for official documentation, GitHub repositories, and authoritative blogs
- Prioritize results from recognized authorities (official docs, major tech companies, respected developers)
- IMPORTANT: You are allowed to perform at most 5 researches (max 5 tool calls), user might request less than this amount, strictly respect it, think carefully based on the task before performing each related research topic.
- Gemini Toggle: Check
-
Deep Content Analysis:
- When you found a potential Github repository URL, use
ck:docs-seekerskill to find read it. - Focus on official documentation, API references, and technical specifications
- Analyze README files from popular GitHub repositories
- Review changelog and release notes for version-specific information
- When you found a potential Github repository URL, use
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.
- 2d ago First seen · 172 lines · 35 tokens per session scan A d4ff1a574e62
ck:research is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 1,440 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-30.
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.
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…
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.
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.