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/zhu1090093659/codeconductor/create-assistantnpx skills add zhu1090093659/CodeConductor --skill create-assistantgit clone --depth 1 https://github.com/zhu1090093659/CodeConductorWrote 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/zhu1090093659/codeconductor/create-assistant)<a href="https://agentmods.dev/skills/zhu1090093659/codeconductor/create-assistant"><img src="https://agentmods.dev/badge/skills/zhu1090093659/codeconductor/create-assistant.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.00074 | $0.01335 |
| Opus 5 | $0.00037 | $0.00668 |
| Sonnet 5 | $0.00015 | $0.00267 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
create-assistant 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Assistant
Guide users through creating custom assistants via interactive dialogue.
CRITICAL: File Path Requirements
STOP! Before creating ANY file, you MUST follow these steps:
- NEVER create files in the current working directory or project folder
- ALWAYS use the CodeConductor system config directory
Required Path
The assistant file MUST be created at:
C:\Users\{username}\AppData\Roaming\CodeConductor\CodeConductor\config\custom-assistants\{id}\{id}.md (Windows)
~/Library/Application Support/CodeConductor/CodeConductor/config/custom-assistants/{id}/{id}.md (macOS)
~/.config/CodeConductor/CodeConductor/config/custom-assistants/{id}/{id}.md (Linux)
How to Get the Correct Path
Step 1: Call ipcBridge.fs.getCustomAssistantsDir first to get the exact path.
Step 2: The result will be something like:
- Windows:
C:\Users\zcl\AppData\Roaming\CodeConductor\CodeConductor\config\custom-assistants - macOS:
/Users/xxx/Library/Application Support/CodeConductor/CodeConductor/config/custom-assistants
Step 3: Create files inside that directory:
- Directory:
{result}/{assistant-id}/ - File:
{result}/{assistant-id}/{assistant-id}.md
WRONG Examples (DO NOT DO THIS)
❌ D:\work\dp2\assistant\xiaohongshu\xiaohongshu.md
❌ ./assistant/my-helper/my-helper.md
❌ ~/.claude/skills/assistant/...
❌ {current-project}/assistant/...
CORRECT Examples
✓ C:\Users\zcl\AppData\Roaming\CodeConductor\CodeConductor\config\custom-assistants\xiaohongshu\xiaohongshu.md
✓ ~/Library/Application Support/CodeConductor/CodeConductor/config/custom-assistants/my-helper/my-helper.md
Important: Inherited Capabilities
Custom assistants automatically inherit ALL capabilities from the main agent:
- All installed MCP tools (file operations, web search, browser automation, etc.)
- All enabled Skills (pdf, docx, pptx, algorithmic-art, frontend-design, etc.)
- All system tools (Read, Write, Bash, Grep, Glob, etc.)
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 · 181 lines · 0 tokens per session scan A d7f424240a2f
create-assistant is a skill published in the GitHub repository zhu1090093659/CodeConductor (80 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,335 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-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.
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…