A coding assistant for setting up projects, reading source code, creating files, and organising folders and code structure.

Use it to create project directories, generate starter files, inspect source code, organise folders, and prepare configuration or documentation files.

It reduces the manual work involved in starting a project or finding and arranging files in an existing codebase.

code-helper — Skill for Claude Code by muhdaliyan/zeer

Install

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.

Any agent

npx skills add muhdaliyan/zeer --skill code-helper

Clone the repo

git clone --depth 1 https://github.com/muhdaliyan/zeer

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/muhdaliyan/zeer/code-helper/github.svg)](https://agentmods.dev/skills/muhdaliyan/zeer/code-helper)

Your own site

<a href="https://agentmods.dev/skills/muhdaliyan/zeer/code-helper"><img src="https://agentmods.dev/badge/skills/muhdaliyan/zeer/code-helper/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/muhdaliyan/zeer/code-helper"><img src="https://agentmods.dev/badge/skills/muhdaliyan/zeer/code-helper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 411 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.1	$0.00036	$0.00411
Opus 5.5	$0.00014	$0.00164
Sonnet 5.5	$0.00007	$0.00082
Haiku 4.5	$0.00004	$0.00041

Measured 1mo ago against content hash 786287891bfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (__init__.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/code-helper/SKILL.md · 66 lines

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)
When working with existing code:
- Use list_directory to explore structure
- Use read_file to examine source files
- Use write_to_file to update code
When creating new code:
- Use create_file with appropriate templates
- Follow language-specific conventions
- Include proper comments and documentation

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

Files

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.

__init__.py 25 B runs code

Changes

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.

1mo ago First seen · 66 lines · 36 tokens per session scan A 786287891bfe

Subscribe to this mod's changes

code-helper is a skill published in the GitHub repository muhdaliyan/zeer (6 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 411 once invoked, about $0.0001 per session on Opus 5.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.

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens