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

Todo

by ploxc in ploxc/modbux

Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight.

MITAuto-check passedDevelopment

Install Todo

skills CLI
$ npx skills add ploxc/modbux --skill todo -a claude-code

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

GitHub CLI
$ gh skill install ploxc/modbux todo --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/ploxc/modbux.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/todo .claude/skills/todo && 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
todo
GitHub stars
108
Token cost
~898 tokens
SKILL.md length
492 words
Files
2 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight.

  • Write that down
  • SKILL.md covers First: is it yours to fix…, Then: state, or history?, TODO.md is not a record and… and Before adding a paragraph to…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Decide whether a change needs a test — that is test

What it does

Todo is an agent skill from ploxc/modbux. Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight. Use before writing down a task, a reason or a defect, and whenever the user says "note that", "write that down" or "add a TODO". Do NOT use to decide whether a change needs a test — that is test.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/the-explanation-that-ate-the-task.md`).

It sits in Development. It works with GitHub. The repository describes itself as: Free open-source Modbus client (master) GUI and server simulator for Windows, macOS and Linux. Desktop tool for Modbus TCP, RTU and RTU over TCP. A modern alternative to Modbus… The licence is MIT.

When your agent uses it

  • Write that down
  • Decide whether a change needs a test — that is test

Example prompts

  • “note that”
  • “write that down”
  • “add a TODO”
  • “/todo”

What it can do on your machine

Read from SKILL.md and the folder at commit 3313c0f. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Todo loads about 898 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 84 tokens; SKILL.md has 492 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~898
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

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 ploxc/modbux at commit 3313c0f, republished under its MIT licence (© ploxc). 492 words, ~898 tokens.

Download SKILL.mdSave it as .claude/skills/todo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
todo
description
Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight. Use before writing down a task, a reason or a defect, and whenever the user says "note that", "write that down" or "add a TODO". Do NOT use to decide whether a change needs a test — that is test.

Todo

First: is it yours to fix instead?

Writing a defect down converts it into a backlog item, and backlog items feel handled. Before choosing a place, choose whether there is one:

  • the fix is small — do it in this commit, and record nothing
  • larger — tell the user, and let them decide
  • the user deferred it — now it goes somewhere, and the rest of this decides where

The tell is the sentence you are about to write. "Pre-existing", "older than this branch", "not mine", "pulled in by proximity". Each of those can be true, and none of them answers whether the fix is small.

Then: state, or history?

what you are writingwhere it goes
something to do, on this branch or the nextTODO.md, one line
something a user would recognise as a bug or a requesta GitHub issue
why — a decision, a measurement, an approach that failedthe memory directory
a preference the user stated, or how they want to workthe memory directory, never the repository
something already in the plan being executedthere, and not twice
what a user can now doCHANGELOG.md, at the release

The tell is the tense. "Enable require-await" is a task. "Two handlers stayed async because reading the version off the store took their only await, and lint has the rule off" is a record. If your sentence explains, it is not a task, however true it is.

The other tell is length. A task is one line, maybe three. The moment you reach for a table, a code block, or a paragraph beginning "the cause is", you are writing a record, and the memory directory is where records go.

Show full SKILL.md (212 more words)Show less

TODO.md is not a record and not shared

It is untracked. It does not survive a clone, it does not reach anyone else, and it does not move with a branch. So:

  • Anything another person needs goes to a GitHub issue instead. A note to yourself is the only thing this file holds.
  • A symbol name is authoritative, a line number is a hint. Name the symbol; a line number goes stale on the next edit above it.
  • A finished item is deleted, never ticked. A ticked box is history, and history in a task list is what makes a task list stop being read.

Before adding a paragraph to something already there

The destination looks settled, so the test above gets skipped — and that is how a task list turns into a history one paragraph at a time.

Read the whole entry first. If your addition explains rather than instructs, the entry stays one line and the explanation goes to memory. → WHY: the explanation that ate the task

What the user says goes where they say

"Note that" and "write that down" name the act, not the destination. Route it by the table, then say in one line where it landed and why, so a wrong call is cheap to correct.

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

Files

SKILL.md and 1 other file (references) in .claude/skills/todo of ploxc/modbux.

  • SKILL.md
  • references/the-explanation-that-ate-the-task.md

Open the folder on GitHubat commit 3313c0f

Compare with similar skills

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

Todo compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Todo this skillploxc/modbux108—~898Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Setup Matt Pocock Skillsbestofjs/bestofjs3.1k20 repos~1.7kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

  • Setup Matt Pocock Skills

    bestofjs/bestofjs

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout.

    3.1k GitHub starsUsed in 20 repos~1.7k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

More from ploxc/modbux

  • Audit

    ploxc/modbux

    Audit one area of Modbux against the eight criteria and write the findings to tmp/AUDIT-<area.md, changing no code.

    108 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Precommit

    ploxc/modbux

    Run the checklist before committing or merging — read the diff, lint, typecheck, the unit suite, the e2e specs the change touches, then report and commit.

    108 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Handover

    ploxc/modbux

    Empty a session into files before its context goes — decide with the user what gets written down, write it, and only then say what the next session needs.

    108 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Prose

    ploxc/modbux

    Measure a sentence you just wrote against the thing it describes, then prune the block it lands in.

    108 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Todo

What does Todo do?

Route something you want to record to the place that holds it — TODO.md, a GitHub issue, the memory directory, or the plan in flight. Todo is an agent skill from ploxc/modbux.md, a GitHub issue, the memory directory, or the plan in flight.

When should I use Todo?

Todo fits situations like: write that down; decide whether a change needs a test — that is test.

How do I install Todo in Claude Code?

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

How do I install Todo in Codex?

Run `npx skills add ploxc/modbux --skill todo -a codex`. Or copy the skill folder (.claude/skills/todo in ploxc/modbux) into .agents/skills/todo in your project. Codex loads it when a task matches its description.

Can I use Todo 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 ploxc/modbux --skill todo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/todo, .gemini/skills/todo, .github/skills/todo and .opencode/skills/todo in your project.

What does Todo need to run?

SKILL.md names no scripts, command-line tools or credentials: Todo is instructions for the agent only.

Does Todo 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 Todo 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 Todo use?

Todo 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 Todo use?

About 898 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 300 tokens, read only when the agent opens those files.

What are the alternatives to Todo?

Skills that share tags, products or a category with Todo: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Setup Matt Pocock Skills (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Todo?

ploxc (a GitHub organization) maintains it in ploxc/modbux, which has 108 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

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