New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Coding Agent

by spytensor in spytensor/openmozi

Structured coding workflow: read, plan, implement, test, verify

MITAuto-check passedTesting & QA

Install Coding Agent

skills CLI
$ npx skills add spytensor/openmozi --skill coding-agent -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install spytensor/openmozi coding-agent --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/coding-agent .claude/skills/coding-agent && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
coding-agent
GitHub stars
439
Token cost
~723 tokens
SKILL.md length
423 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Structured coding workflow: read, plan, implement, test, verify

  • Works in 5 steps: Read & Understand → Plan → Implement → …
  • Testing & QA work in your project
  • SKILL.md covers When to Use, How to Execute, Examples and Edge Cases
  • Calls pnpm

What it does

Coding Agent is an agent skill from spytensor/openmozi. Structured coding workflow: read, plan, implement, test, verify

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with TypeScript and pnpm. The repository describes itself as: A custom Agent OS built to be hackable, heavily inspired by OpenClaw. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/coding-agent”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Read & Understand
  2. Plan
  3. Implement
  4. Test
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit ac46df0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Coding Agent loads about 723 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 423 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~723

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from spytensor/openmozi at commit ac46df0, republished under its MIT licence (© spytensor). 423 words, ~723 tokens.

Download SKILL.mdSave it as .claude/skills/coding-agent/SKILL.md (or your agent's skills folder).
name
coding-agent
description
Structured coding workflow: read, plan, implement, test, verify
version
1.0.0
category
coding
user-invocable
true
always
true
metadata.priority
80

Coding Agent

When to Use

  • User asks to implement a feature, fix a bug, or modify code
  • User asks to build, create, or set up a project or component
  • Any task that involves writing or modifying source code
  • Always active: enforces the structured workflow for all coding tasks

How to Execute

Phase 1: Read & Understand
  1. Read the relevant source files to understand the current state.
  2. Identify the exact files, functions, and lines that need to change.
  3. Check for existing tests, types, and conventions in the codebase.
  4. Read any related config files, schemas, or documentation.
Phase 2: Plan
  1. State what will change and what will NOT change.
  2. List every file to be modified or created.
  3. If the change is non-trivial (>20 lines), describe the approach before writing code.
  4. If the request conflicts with existing architecture, state the conflict and options.
  5. Get user confirmation on the plan for large changes.
Phase 3: Implement
  1. Make the minimum change that satisfies the requirement.
  2. Match existing code style — indentation, naming, patterns.
  3. Add JSDoc to public functions. Use TypeScript strict types.
  4. Handle errors explicitly — no silent swallows, no bare catch {}.
  5. Add timeouts to external I/O calls.
  6. Do NOT refactor unrelated code unless explicitly asked.
Phase 4: Test
  1. Run existing tests to ensure nothing is broken: pnpm test.
  2. If new behavior was added, write tests that prove it works.
  3. Tests must cover: happy path, error case, edge case.
  4. Mock external boundaries in unit tests; keep real provider calls in explicit integration tests.
Show full SKILL.md (159 more words)Show less
Phase 5: Verify
  1. Run pnpm build to confirm TypeScript compiles cleanly.
  2. Run pnpm test to confirm all tests pass.
  3. List every file modified and summarize each change.
  4. Identify the most likely failure point in the new code.

Examples

Input: "Add a health check endpoint to the API" Workflow: Read index.ts and Fastify setup → Plan: add GET /health route → Implement the route → Write test → Verify build + tests pass.

Input: "Fix the timeout error in shell execution" Workflow: Read capabilities/shell.ts → Find the timeout logic → Identify the bug → Fix it → Run existing tests → Verify.

Edge Cases

  • If tests fail after the change, fix the issue before reporting success.
  • If the build fails with type errors, resolve them — do not skip with any.
  • If the task requires a dependency, check package.json first; install only if truly needed.
  • If the user's request is vague, ask for clarification rather than guessing.
  • Never claim "this should work" without running build and tests.

© spytensor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/coding-agent of spytensor/openmozi.

Open the folder on GitHubat commit ac46df0

Compare with similar skills

Coding Agent next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Coding Agent compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Coding Agent this skillspytensor/openmozi439—~723Automated safety check: PassMIT
Ha Frontend Testinghome-assistant/frontend5.7k—~1.7kAutomated safety check: PassApache-2.0
Preshipopenplayerjs/openplayerjs649—~1.2kAutomated safety check: PassMIT
Parse Error Logsmaslennikov-ig/claude-code-orchestrator-kit259—~1.5kAutomated safety check: PassCustom licence
Stryker JSmizchi/skills356—~2.4kAutomated safety check: PassNone
Optimizeopenplayerjs/openplayerjs649—~1.9kAutomated safety check: PassMIT

Similar skills

  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Preship

    openplayerjs/openplayerjs

    Run the full OpenPlayerJS verification gauntlet before committing, opening a PR, or preparing a release.

    649 GitHub stars~1.2k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Parse Error Logs

    maslennikov-ig/claude-code-orchestrator-kit

    Parse build errors, test failures, type-check output, and validation logs into structured data.

    259 GitHub stars~1.5k tokensUpdated 7 mo ago
    Testing & QAAuto-check passed

  • Stryker JS

    mizchi/skills

    Introduce StrykerJS mutation testing or assess JavaScript/TypeScript test quality.

    356 GitHub stars~2.4k tokensUpdated 5 days ago
    Testing & QAAuto-check passed

  • Optimize

    openplayerjs/openplayerjs

    Find and safely apply ONE worthwhile code optimization (reuse, simplification, efficiency, or a dead-weight cleanup) somewhere in packages//src, with new regression tests proving behavior is…

    649 GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Repo Healthcheck Node

    commercetools/ui-kit

    Verify a Node.js/TypeScript repo's development environment is correctly set up.

    154 GitHub stars~1.6k tokensUpdated 4 days ago
    Frontend & DesignAuto-check: notes

More from spytensor/openmozi

All 13 skills in this repo

  • Commit

    spytensor/openmozi

    Smart commit: bump version, find related issues, commit with Co-authored-by, push.

    439 GitHub stars~480 tokensUpdated 2 mo ago
    Auto-check passed

  • Pipeline

    spytensor/openmozi

    Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue.

    439 GitHub stars~549 tokensUpdated 2 mo ago
    Auto-check passed

  • Skill Authoring

    spytensor/openmozi

    How to install a skill package a user hands over (.skill/.zip/.tar.gz), and how to write a new skill into this runtime so it is listed, enabled and usable.

    439 GitHub stars~1.3k tokensUpdated 2 mo ago
    Auto-check passed

  • Research Workflow

    spytensor/openmozi

    Structured research workflow: decompose the question, search in parallel, cross-verify sources, synthesize with citations.

    439 GitHub stars~594 tokensUpdated 2 mo ago
    Auto-check passed

  • Self Ops

    spytensor/openmozi

    Runtime self-diagnosis knowledge: database layout, observability APIs, timeout hierarchy, restart procedure, failure replay.

    439 GitHub stars~767 tokensUpdated 2 mo ago
    Auto-check passed

  • Creative Writing

    spytensor/openmozi

    Creative content workflow: brief, research, outline, draft, refine.

    439 GitHub stars~373 tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Coding Agent

What does Coding Agent do?

Structured coding workflow: read, plan, implement, test, verify. Coding Agent is an agent skill from spytensor/openmozi.

When should I use Coding Agent?

Coding Agent fits situations like: testing & QA work in your project.

How do I install Coding Agent in Claude Code?

Run `npx skills add spytensor/openmozi --skill coding-agent -a claude-code`. Or copy the skill folder (skills/coding-agent in spytensor/openmozi) into .claude/skills/coding-agent in your project. Claude Code loads it when a task matches its description.

How do I install Coding Agent in Codex?

Run `npx skills add spytensor/openmozi --skill coding-agent -a codex`. Or copy the skill folder (skills/coding-agent in spytensor/openmozi) into .agents/skills/coding-agent in your project. Codex loads it when a task matches its description.

Can I use Coding Agent in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spytensor/openmozi --skill coding-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coding-agent, .gemini/skills/coding-agent, .github/skills/coding-agent and .opencode/skills/coding-agent in your project.

What does Coding Agent need to run?

Going by SKILL.md and its folder, Coding Agent needs the command-line tools its instructions call (pnpm).

Does Coding Agent access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Coding Agent safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Coding Agent use?

Coding Agent is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Coding Agent use?

About 723 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Coding Agent?

Skills that share tags, products or a category with Coding Agent: Ha Frontend Testing (home-assistant/frontend, 5.7k stars), Preship (openplayerjs/openplayerjs, 649 stars), Parse Error Logs (maslennikov-ig/claude-code-orchestrator-kit, 259 stars) and Stryker JS (mizchi/skills, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Coding Agent?

spytensor (a GitHub user) maintains it in spytensor/openmozi, which has 439 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 7, 2026.

Source: spytensor/openmozi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.