cli-usage

cli-usage is a skill for Claude Code, Codex from hugoduncan/mcp-tasks. It costs 0 tokens per session (3,251 once invoked), scanned A, original, EPL-2.0.

A reference guide for the mcp-tasks command-line tool, which lets developers work with tasks from a terminal. The input does not provide further details about its commands or supported operations.

In plain words
What is it for?
It is intended for looking up mcp-tasks CLI usage, but the input does not say which concrete commands or workflows are covered.
Why use it?
Use it when you need command-line instructions for mcp-tasks and want to check the correct syntax. The available information is too limited to describe specific tasks it performs.

Skill for Claude CodeCodex

Part of the mcp-tasks-cli plugin — 1 skill shipped together

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.

agentmods
npx agentmods add skills/hugoduncan/mcp-tasks/cli-usage
Any agent
npx skills add hugoduncan/mcp-tasks --skill cli-usage
Clone the repo
git clone --depth 1 https://github.com/hugoduncan/mcp-tasks

Made for: Claude Code, Codex.

Or install mcp-tasks-cli, the plugin that ships this one along with the rest of its 1 skill.

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 cli-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/hugoduncan/mcp-tasks/cli-usage.svg)](https://agentmods.dev/skills/hugoduncan/mcp-tasks/cli-usage)
Your own site
<a href="https://agentmods.dev/skills/hugoduncan/mcp-tasks/cli-usage"><img src="https://agentmods.dev/badge/skills/hugoduncan/mcp-tasks/cli-usage.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,251 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00000 $0.03251
Opus 5 $0.00000 $0.01625
Sonnet 5 $0.00000 $0.00650
Haiku 4.5 $0.00000 $0.00325

Measured 3d ago against content hash cc46dd9d89de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-usage 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.

plugins/mcp-tasks-cli/skills/cli-usage/SKILL.md · 411 lines

The source is not reproduced here

Licensed EPL-2.0

The repository is licensed EPL-2.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 411 lines · 0 tokens per session scan A cc46dd9d89de

Subscribe to this mod's changes

cli-usage is a skill published in the GitHub repository hugoduncan/mcp-tasks (11 stars, last pushed 6mo ago), licensed EPL-2.0. It costs nothing until one of its globs matches a file; then it loads 3,251 tokens. 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

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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