ModsCode / Claude Code Mods / Ranking / backlog-board
backlog-board
Sidebar pane showing virtual-team backlog progress (backlog.md, features/, handoffs/)
What it does
- Draws a pane, toasts
- Adds /board
- Hooks session.start, turn.complete
- Keeps its own state between turns
Good points
- No network calls
- Starts no processes
- Written in TypeScript
- Handles errors
Code to start from
A starter ModsCode writes from the drawing it read, and the mod's own lines that draw, where there are any.
Starter (register.tsx)
import type { Register } from 'claude-code'
// Drawn like backlog-board by Luis Capobianco (pane, toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/the-cmo-lab-backlog-board/
// Written by ModsCode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
// the pane: open it with $.ui.open({ id: 'my-pane', title: "Backlog" })
on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
const { Box, Button, Text } = $.ui.resolve(e)
const pct = '…'
const done = '…'
const total = '…'
const prog = '…'
const verify = '…'
const blocked = '…'
const todo = '…'
const parked = '…'
const dir = '…'
const dir2 = '…'
const dir3 = '…'
const length = '…'
const title = '…'
const title2 = '…'
const title3 = '…'
const length2 = '…'
const title4 = '…'
const title5 = '…'
const title6 = '…'
const length3 = '…'
const title7 = '…'
const title8 = '…'
const title9 = '…'
const length4 = '…'
const title10 = '…'
const title11 = '…'
const title12 = '…'
const date = '…'
const title13 = '…'
const docsDir = '…'
return (
<Box flexDirection="column">
<Box flexDirection="row" gap={1}>
<Button hotkey="o" variant="primary" label="Overview" />
<Button hotkey="f" variant="primary" label="Features" />
<Button hotkey="r" label="Refresh" />
</Box>
<Box marginTop={1}>
<Text>
<Text bold>
{pct}
{"% done "}
</Text>
<Text color="success">
████████░░░░░░░░
</Text>
<Text dimColor>
{" "}
{done}
/
{total}
</Text>
</Text>
</Box>
<Text wrap="wrap">
<Text color="warning">
{"● "}
{prog}
{" doing"}
</Text>
{" "}
<Text color="suggestion">
{"◐ "}
{verify}
{" verify"}
</Text>
{" "}
<Text color="error">
{"✕ "}
{blocked}
{" blocked"}
</Text>
{" "}
<Text>
{"○ "}
{todo}
{" ready"}
</Text>
<Text dimColor>
{" · "}
{parked}
{" parked"}
</Text>
</Text>
<Text dimColor italic wrap="wrap">
{dir}
</Text>
<Text dimColor italic wrap="wrap">
{dir2}
</Text>
<Text dimColor italic wrap="wrap">
{dir3}
</Text>
<Box flexDirection="column" marginTop={1}>
<Text bold color="warning">
In progress
{" "}
<Text dimColor>
{length}
</Text>
</Text>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title2}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title3}
</Text>
</Button>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold color="suggestion">
Verify
{" "}
<Text dimColor>
{length2}
</Text>
</Text>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title4}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title5}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title6}
</Text>
</Button>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold color="error">
Blocked
{" "}
<Text dimColor>
{length3}
</Text>
</Text>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title7}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title8}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title9}
</Text>
</Button>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold color="text">
Next up
{" "}
<Text dimColor>
{length4}
</Text>
</Text>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title10}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title11}
</Text>
</Button>
<Button plain>
<Text>
•
</Text>
{" "}
<Text>
{title12}
</Text>
</Button>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold>
Last handoff
</Text>
<Text wrap="truncate-end">
<Text dimColor>
{date}
</Text>
{" "}
{title13}
</Text>
</Box>
<Text dimColor>
Select an item to see its details.
</Text>
<Box marginTop={1}>
<Text dimColor wrap="truncate-middle">
{docsDir}
{"/backlog.md · "}
read failed
</Text>
</Box>
</Box>
)
})
on('session.start', async ($, e, next) => {
await $.ui.toast(`Backlog changed — board updated`)
return next(e)
})
}
The mod's own code
Its licence text was not found at the commit read, so only the places in the source are linked.
How to build this: Pane (panel), Add a slash command
What its code calls
reads filesremembers
What its code shows
Read from the source at commit c867a424a0a0 on 2026-10-11. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.
| Decides the listing: code you can check | |
|---|---|
| Entry read | Every module hooks/hooks.json names was read.plugins/backlog-board/hooks/register.tsx |
| Parses | Every file parses as TypeScript or JavaScript.2 files parsed |
| All its code is in the mod | Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod |
| Readable | No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs |
| Calls in the open | Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open |
| For you to weigh before installing | |
| Where it draws | The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both |
| Install line | Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there |
| Programs on Windows | Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks |
| Network | Whether every fetch names its https host in the code.no network |
| Programs | Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.starts no programs |
| Reads and sends | Whether it both reads something of yours (files, environment variables, the transcript, settings) and reaches outside (the network, an MCP server, another session, telemetry).reads files, but reaches nothing outside |
| Keys in the source | Whether the source holds what looks like an API key or a private key.no keys in the source |
| Licence | An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets ModsCode show its code; otherwise the code is linked.no licence |
| Settings hooks | Hooks declared in hooks/hooks.json or plugin.json beside the module: a command (a shell when it has no args), an HTTP request, an MCP tool or a model prompt at an event. They run outside $.no settings hooks: its function hooks alone |
| Servers it ships | MCP servers (a program, or a URL; a headersHelper is a shell command; a .mcpb bundle is unpacked at run time), LSP servers, monitors (a shell command for the whole session) and bin/ (on the PATH of the Bash tool).ships no MCP or LSP server, no monitor, no bin/ |
| Skills, commands, agents | What its Markdown declares beyond text: allowed-tools granted for the turn, hooks added when a skill is invoked, a command run before Claude reads the skill.no skills, commands, agents or workflows |
| Tools and MCP | Whether every tool it calls through $.tool.call and $.mcp.call is named in the code, and none is a shell (Bash through the tool runs a shell without $.process).calls no tool, MCP server or command |
| Asks of the model | Completions it runs ($.model.complete, fork, classify), subagents it spawns, prompts it submits as you, and the tools, commands and agents it adds.adds command board |
| Events it hooks | By what a hook there can do: gates (refuse a tool call, a prompt, a setting, another plugin), shapes (what the model reads: the system prompt, tool descriptions, each request), reads (your input, the events of the settings hooks, every event with *), and the rest.gates: command.run (board) · also: session.start, turn.complete, ui.render (Pane) · timers: clock.every |
| Reads, by name | The environment variables and files it names, and whether it reads the transcript, settings.json, the prompt box or the mouse selection.files: a path computed at run time |
| Writes, by name | The files and environment variables it names, and whether it changes settings, the prompt box, the clipboard, the conversation (a row the model reads) or another session.writes no files, environment variables, settings or conversation rows |
This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen
Install it
Check it yourself before you install it. Mods run unsandboxed, with your permissions, and ModsCode does not vouch for what this code does. Read its code (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.
From its marketplace
Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:
/plugin marketplace add The-CMO-Lab/development/plugin install backlog-board@development/reload-pluginsThis installs the marketplace's latest commit, which may not be the one read here (c867a424a0a0). Compare them before you install. /reload-plugins loads it into a session that is already open.
Try the commit ModsCode read
No marketplace needed. In a terminal, clone the repository, check out the commit read, validate the mod, and load it for one session:
git clone https://github.com/The-CMO-Lab/developmentgit -C development checkout c867a424a0a05277c37d3b0e27d492f99bedd3ddclaude plugin validate development/plugins/backlog-boardclaude --plugin-dir development/plugins/backlog-boardThe validate line lists the events the mod hooks and what it asks Claude Code to do, without running it. The last line loads the mod for this session only and writes nothing to your settings. If the author has rewritten history, the commit may no longer exist.
Ask Claude about it
With the ModsCode connector added, Claude can read this mod's code and what it reaches, and build on them. Ask it like this:
Read the ModsCode mod "the-cmo-lab-backlog-board" with its code and make me one like itSearch them from Claude: the MCP connector
Similar mods
- cscs★ 47
- modtestdstoic★ 20
- stoadstoic★ 20
- qa-guideaieo-product★ 11
- roadraven-hudShuffzord★ 6
- glossary-browserFabrizio Duroni★ 5
Badge for your README
If this is your mod, paste this into your README. It links to this page.
[](https://modscode.com/claude-mods/mods/the-cmo-lab-backlog-board/)