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/muhdaliyan/zeer/code-helpernpx skills add muhdaliyan/zeer --skill code-helpergit clone --depth 1 https://github.com/muhdaliyan/zeerWhat 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.00036 | $0.00411 |
| Opus 5 | $0.00018 | $0.00205 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
code-helper 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 3d 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.
What it actually says
Goal
Assist developers with common coding tasks including project setup, file organization, and code management.
Capabilities
Project Setup
- Create project directory structures
- Generate boilerplate files
- Set up configuration files
Code Management
- Read and analyze source files
- Create new code files with templates
- Organize code into proper directory structures
File Organization
- List project files
- Navigate project structure
- Create organized folder hierarchies
Procedure
-
When setting up a new project:
- Create root directory with
make_directory - Create subdirectories (src, tests, docs, etc.)
- Generate initial files (README, config files)
- Create root directory with
-
When working with existing code:
- Use
list_directoryto explore structure - Use
read_fileto examine source files - Use
write_to_fileto update code
- Use
-
When creating new code:
- Use
create_filewith appropriate templates - Follow language-specific conventions
- Include proper comments and documentation
- Use
Best Practices
- Always check if files exist before creating
- Use consistent naming conventions
- Organize code into logical directories
- Include README files for documentation
- Add comments to explain complex logic
Examples
User: "Set up a Python project" → Create directories: src/, tests/, docs/ → Create files: README.md, requirements.txt, setup.py
User: "Show me the project structure"
→ Use list_directory recursively
User: "Create a new Python module for database operations"
→ Use create_file with path="src/database.py" and appropriate template
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 66 lines · 36 tokens per session scan A 786287891bfe
code-helper is a skill published in the GitHub repository muhdaliyan/zeer (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 411 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.
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…