ModsCode / Claude Code Mods / Ranking / clayfold-monitor
clayfold-monitor
Clayfold server and frontend statistics and the Claude Code instances the server runs, in a pane
What it does
- Draws a pane, toasts
- Watches tool calls
- Hooks session.start
- Calls the network
- Starts processes
Good points
- Small: 348 lines
- Written in TypeScript
- Has a desktop-specific branch
- 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 clayfold-monitor by VinniZP (pane, status, toast), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/vinnizp-clayfold-monitor/
// 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: "Clayfold" })
on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
const { Box, Text, Link, Button } = $.ui.resolve(e)
const since = '…'
const appUrl = '…'
const pid = '…'
const bun = '…'
const port = '…'
const mb = '…'
const mb2 = '…'
const pct = '…'
const mb3 = '…'
const model = '…'
const criticModel = '…'
const usd = '…'
const vitePort = '…'
const streams = '…'
const length = '…'
const kind = '…'
const elapsed = '…'
const label = '…'
const label2 = '…'
const label3 = '…'
const instanceMeta = '…'
const key = '…'
const kind2 = '…'
const elapsed2 = '…'
const label4 = '…'
const label5 = '…'
const label6 = '…'
const instanceMeta2 = '…'
const kind3 = '…'
const elapsed3 = '…'
const label7 = '…'
const label8 = '…'
const label9 = '…'
const instanceMeta3 = '…'
const finishedText = '…'
const since2 = '…'
const finishedText2 = '…'
const since3 = '…'
const finishedText3 = '…'
const since4 = '…'
return (
<Box flexDirection="column">
<Text>
<Text bold>
Backend
</Text>
{" "}
<Text color="green">
up
</Text>
{" "}
{since}
{" "}
<Link href={`${appUrl}`} label="open app" />
</Text>
<Text wrap="truncate-end">
{"PID "}
{pid}
{" · Bun "}
{bun}
{" · :"}
{port}
</Text>
<Text wrap="truncate-end">
{mb}
{" (heap "}
{mb2}
{") · CPU "}
{pct}
{" · DB "}
{mb3}
</Text>
<Text dimColor wrap="truncate-end">
{model}
{", critic "}
{criticModel}
{" · "}
{usd}
{" per run"}
</Text>
<Text>
{" "}
</Text>
<Text bold>
Frontend
</Text>
<Text wrap="truncate-end">
{"web/dist "}
{`built ${since} ago`}
</Text>
<Text>
Vite :
{vitePort}
{" "}
<Text color="green">
up
</Text>
</Text>
<Text dimColor>
{streams}
{" open event stream"}
</Text>
<Text>
{" "}
</Text>
<Text bold>
{"Claude Code instances: "}
{length}
</Text>
<Text dimColor>
None running.
</Text>
<Box flexDirection="column" marginTop={1}>
<Text wrap="truncate-end">
<Text color="magenta">
{kind}
</Text>
{" "}
<Text bold>
—
</Text>
{" "}
<Text color="yellow">
{elapsed}
{" long run"}
</Text>
</Text>
<Text wrap="truncate-end">
{" "}
{label}
</Text>
<Text wrap="truncate-end">
{" "}
{label2}
</Text>
<Text wrap="truncate-end">
{" "}
{label3}
</Text>
<Text dimColor wrap="truncate-end">
{instanceMeta}
</Text>
<Box flexDirection="row" gap={2}>
<Button hotkey={`${key}`} dimColor>
stop
</Button>
<Link href={`${appUrl}`} label="open in browser" />
</Box>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text wrap="truncate-end">
<Text color="magenta">
{kind2}
</Text>
{" "}
<Text bold>
—
</Text>
{" "}
<Text color="yellow">
{elapsed2}
{" long run"}
</Text>
</Text>
<Text wrap="truncate-end">
{" "}
{label4}
</Text>
<Text wrap="truncate-end">
{" "}
{label5}
</Text>
<Text wrap="truncate-end">
{" "}
{label6}
</Text>
<Text dimColor wrap="truncate-end">
{instanceMeta2}
</Text>
<Box flexDirection="row" gap={2}>
<Button hotkey={`${key}`} dimColor>
stop
</Button>
<Link href={`${appUrl}`} label="open in browser" />
</Box>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text wrap="truncate-end">
<Text color="magenta">
{kind3}
</Text>
{" "}
<Text bold>
—
</Text>
{" "}
<Text color="yellow">
{elapsed3}
{" long run"}
</Text>
</Text>
<Text wrap="truncate-end">
{" "}
{label7}
</Text>
<Text wrap="truncate-end">
{" "}
{label8}
</Text>
<Text wrap="truncate-end">
{" "}
{label9}
</Text>
<Text dimColor wrap="truncate-end">
{instanceMeta3}
</Text>
<Box flexDirection="row" gap={2}>
<Button hotkey={`${key}`} dimColor>
stop
</Button>
<Link href={`${appUrl}`} label="open in browser" />
</Box>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold>
Recently finished
</Text>
<Text wrap="truncate-end" color="red">
{finishedText}
{" · "}
{since2}
{" ago"}
</Text>
<Text wrap="truncate-end" color="red">
{finishedText2}
{" · "}
{since3}
{" ago"}
</Text>
<Text wrap="truncate-end" color="red">
{finishedText3}
{" · "}
{since4}
{" ago"}
</Text>
</Box>
</Box>
)
})
on('session.start', async ($, e, next) => {
const message = '…'
await $.ui.toast(`Clayfold: stopping the run…`)
await $.ui.toast(`Clayfold: stop failed: ${message}`)
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), Deny a tool call
What its code calls
networkruns programsreads filestool calls
What its code shows
Read from the source at commit a5f8ed84c832 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..claude/skills/clayfold-monitor/hooks/register.tsx |
| Parses | Every file parses as TypeScript or JavaScript.1 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.its repository's .claude-plugin/marketplace.json does not list it: no marketplace line to give; the page shows how to try the commit read |
| 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..claude/skills/clayfold-monitor/hooks/register.tsx:92 fetch(`http://127.0.0.1:${port}/api/system`); .claude/skills/clayfold-monitor/hooks/register.tsx:108 fetch(`http://localhost:${config.vitePort}/`); .claude/skills/clayfold-monitor/hooks/register.tsx:133 fetch(`http://127.0.0.1:${port}/api/conversations/${enco) |
| Programs | Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool..claude/skills/clayfold-monitor/hooks/register.tsx:159 bun (a shell or interpreter) |
| 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 and reaches the network |
| 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.AGPL-3.0 (not an open 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 ?, adds tool ? |
| 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, tool.call · also: session.start, 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: …/server/index.ts |
| 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.
Its repository's .claude-plugin/marketplace.json does not list it, so there is no marketplace line to give.
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/VinniZP/clayfoldgit -C clayfold checkout a5f8ed84c832c4aaa17d5c4a27baaf736ca34874claude plugin validate clayfold/.claude/skills/clayfold-monitorclaude --plugin-dir clayfold/.claude/skills/clayfold-monitorThe 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 "vinnizp-clayfold-monitor" with its code and make me one like itSearch them from Claude: the MCP connector
Similar mods
- explain-asSumit Paul★ 20
- cc-pr-trackerSeza Akgün★ 5
- tracenadav-grs★ 3
- pr-inbox2bo★ 2
- ci-autopilotmako-code★ 1
- gh-inboxmako-code★ 1
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/vinnizp-clayfold-monitor/)