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.
git clone --depth 1 https://github.com/moshcoder/moshcodeWrote 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.
[](https://agentmods.dev/commands/moshcoder/moshcode/start)<a href="https://agentmods.dev/commands/moshcoder/moshcode/start"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/start/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.
<a href="https://agentmods.dev/commands/moshcoder/moshcode/start"><img src="https://agentmods.dev/badge/commands/moshcoder/moshcode/start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00015 | $0.00329 |
| Opus 5.5 | $0.00006 | $0.00132 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
start 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.
What it actually says
Task
Start a clock for $ARGUMENTS.
timer start $ARGUMENTS --json
The first word is the project; everything after it is the task, so no quoting is needed. Useful flags:
--agents N— how many engines are working. An agent-priced rate multiplies by this, so it is the difference between a $400 afternoon and a $1,600 one.--at 09:15or--at -20m— the clock you meant to start earlier.--tag,--note,--no-billable.
Rules
- Do not pass
--switchunless the user asked to stop their other clocks. Several clocks running at once is normal here: parallel agents each track their own work, and stopping someone else's is not recoverable from the log. - If
started.alsoRunningcomes back non-empty, mention how many other clocks are running. Do not stop them. - Report the entry id —
timer stop --id <id>needs it, and so does the user if they want to correct the entry later. - If the command exits 2, the command line was wrong; read the error and fix it rather than retrying the same thing.
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.
- 1mo ago First seen · 34 lines · 15 tokens per session scan A ed6127a90ded
start is a command published in the GitHub repository moshcoder/moshcode (3 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 329 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.