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.
npx agentmods add skills/laiso/cman/cm-statusnpx skills add laiso/cman --skill cm-statusgit clone --depth 1 https://github.com/laiso/cmanWrote 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/skills/laiso/cman/cm-status)<a href="https://agentmods.dev/skills/laiso/cman/cm-status"><img src="https://agentmods.dev/badge/skills/laiso/cman/cm-status.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00621 |
| Opus 5 | $0.00013 | $0.00311 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
cm-status 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Show an overview of current Claude Code, Pi Coding Agent, and Codex activity.
Instructions
First, gather data by calling these tools in parallel:
mcp__plugin_cman_cman__list_plansmcp__plugin_cman_cman__list_sessionswith limit=10 and exclude_subagents=truemcp__plugin_cman_cman__list_memorymcp__plugin_cman_cman__list_pi_sessionswith limit=10mcp__plugin_cman_cman__list_codex_sessionswith limit=10
Then use the results to generate the output.
Scope
- Default: Show only entries matching the current working directory.
- If
$ARGUMENTScontainsall: Show entries from all projects.
To determine the current project, use the last component of the current working directory. Filter plans, sessions, and memory by matching the project/cwd path.
Output format
## Status
### Active Plans
| # | Plan | Sessions | Project |
|---|------|----------|---------|
| 1 | {title} | {count} | {project} |
### Recent Sessions
| # | Agent | Title | Project | When | CLI Resume |
|---|-------|-------|---------|------|------------|
| 1 | Claude | {title} | {project} | {relative_time} | `cd {cwd} && claude --resume {session_id}` |
| 2 | Pi | {title} | {project} | {relative_time} | `cd {cwd} && pi --session {session_id}` |
| 3 | Codex | {title} | {project} | {relative_time} | `cd {cwd} && codex resume {session_id}` |
### Memory Overview
- {project}: {count} files
- `{full_path_to_file_1}`
- `{full_path_to_file_2}`
- Keep it scannable — tables for plans and sessions, bullet list for memory.
- For the "Project" column, extract the last directory component from the
cdpath. - If there are no active plans, say "No active plans" instead of an empty table.
- For the CLI Resume column, use the exact resume command shown by the MCP tool.
- For the Title column, rephrase raw prompts into brief work descriptions (e.g., "@README.md" → "README editing", "/remember test" → "Search testing").
- For Memory Overview, always include the full file path (e.g.,
~/.claude/projects/-Users-.../memory/filename.md) for each file listed in the data.
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.
- 3d ago First seen · 59 lines · 25 tokens per session scan A 74c62592e42c
cm-status is a skill published in the GitHub repository laiso/cman (37 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 621 once invoked, about $0.0001 per session on Opus 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…