coding-tools

coding-tools is a skill for Claude Code, Codex from markus-global/markus. It costs 34 tokens per session (3,023 once invoked), scanned A, original, Apache-2.0.

A guide for delegating coding tasks to Claude Code, Codex, or Cursor through command-line tools. It covers both running a coding tool and applying its changes.

In plain words
What is it for?
Implementing, debugging, refactoring, exploring, and committing changes across one or more code files.
Why use it?
It helps choose an external coding assistant for substantial repository work and explains how to check whether each tool is installed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

Good fit Implementing, debugging, refactoring, exploring, and committing changes across one or more code files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markus-global/markus/coding-tools
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 markus-global/markus --skill coding-tools
Clone the repo
git clone --depth 1 https://github.com/markus-global/markus

Made for: Claude Code, Codex.

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.

agentmods badge for coding-tools

README.md
[![agentmods](https://agentmods.dev/badge/skills/markus-global/markus/coding-tools/github.svg)](https://agentmods.dev/skills/markus-global/markus/coding-tools)
Your own site
<a href="https://agentmods.dev/skills/markus-global/markus/coding-tools"><img src="https://agentmods.dev/badge/skills/markus-global/markus/coding-tools/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.

agentmods 80×15 button for coding-tools

Your own site · 80×15
<a href="https://agentmods.dev/skills/markus-global/markus/coding-tools"><img src="https://agentmods.dev/badge/skills/markus-global/markus/coding-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,023 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00034 $0.03023
Opus 5.5 $0.00014 $0.01209
Sonnet 5.5 $0.00007 $0.00605
Haiku 4.5 $0.00003 $0.00302

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

Security

Grade A, and why

coding-tools 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.

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.

templates/skills/coding-tools/SKILL.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coding Tools

Markus can delegate hands-on coding work to external CLI tools. You have two built-in tools for this workflow:

Tool Purpose
invoke_coding_tool Run Claude Code, Codex, or Cursor Agent against a repository with a prompt
coding_tool_apply Commit the changes produced by a coding tool session

Use these when the task requires substantial code changes across multiple files, when you want a specialized coding agent to explore a codebase, or when direct editing would be slower or less reliable than delegating to a dedicated tool.

Available Coding Tools

Tool name CLI binary Best for
claude-code claude Complex refactors, multi-file changes, deep exploration, architecture-level edits
codex codex Quick fixes, targeted patches, scripted automation, fast iteration
cursor-agent cursor IDE-heavy work, projects with .cursor/rules, repo-specific conventions

Check availability with markus doctor before relying on a tool. If a tool is not installed, the handler returns an installHint.

When to Use External Tools vs Write Code Directly

Use external coding tools when:

  • The change spans many files or requires broad codebase exploration
  • You need an autonomous agent to iterate (edit → test → fix) inside the repo
  • The task is well-scoped with clear acceptance criteria but large implementation surface
  • You are coordinating work and want a specialist tool to execute while you review results

Write code directly (file_edit, shell_execute) when:

  • The change is small — a few lines in one or two files
  • You already know exactly what to change and where
  • You need fine-grained control over every edit
  • The task is configuration, documentation, or non-code work

Rule of thumb: If you would open an IDE and spend 15+ minutes navigating and editing, prefer invoke_coding_tool. If you can describe the exact diff in one paragraph, edit directly.

How to Invoke a Coding Tool

Read the full file on GitHub · 301 lines

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.

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.

  1. 1mo ago First seen · 301 lines · 34 tokens per session scan A 7b3e92963b98

Subscribe to this mod's changes

coding-tools is a skill published in the GitHub repository markus-global/markus (205 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 3,023 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-30.

Related

Other skills, from other repositories

muse-governance

Governance behavior for Muse agents governed by DashClaw. Teaches the governance protocol over REST: when to call guard, how to interpret allow/warn/block/requireapproval, recording actions and outcomes, plan-first execution with preflight approval, and waiting for human review. Trigger on: governed agent, dashclaw…

ucsandman/DashClaw · 88 tokens

openai-whisper-api

Transcribe audio via OpenAI Audio Transcriptions API (Whisper).

spinabot/brigade · 20 tokens

ppt-review

Read this skill before the first deck or output quality review, so its criteria are available when the rendered images arrive. Apply the criteria to current officereview structural output and relevant rendered images. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck…

Orkas-AI/Orkas · 2 tokens

seo-crawl

Agent-wide core connector rule: when any connected search console is used, discover its operations with listconnectortools and invoke each selected operation through callconnectortool; naming listsites or an analytics operation without the core invocation is not execution.

Orkas-AI/Orkas · 3 tokens

material-organizer

Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.

Orkas-AI/Orkas · 3 tokens

swiftui-dev

Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.

Orkas-AI/Orkas · 3 tokens