How do I install the Cwd Rollup skill?

Run npx skillmds@latest add hoangsonww/cwd-rollup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cwd Rollup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cwd Rollup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cwd Rollup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cwd Rollup?

hoangsonww (@hoangsonww) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cwd Rollup by hoangsonww — Agent Skill

Name: Cwd Rollup
Rating: 4.2 (5 reviews)
Author: hoangsonww

Cwd Rollup

Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.

hoangsonww Updated Sep 10, 2026

File contents

CWD Rollup

Aggregate session activity per working directory (project).

Input

The user provides: $ARGUMENTS

Empty → roll up all working directories.
A path / project substring → restrict the rollup to matching cwds.
top N → keep only the N highest-cost (or highest-count) projects.

Data Sources

Endpoint	Returns
`GET /api/run/cwds`	the distinct working directories that have sessions — the rollup key set
`GET /api/sessions?limit=N`	session list: id, status, model, cwd, started_at, ended_at, cost, metadata (usage_extras with token counts)
`GET /api/pricing/cost`	fleet cost: total_cost, breakdown[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] — for the fleet total to compute each cwd's share

Report Sections

1. Key set

GET /api/run/cwds for the canonical list of working directories. Apply the $ARGUMENTS filter (substring match) if one was given.

2. Pull sessions

GET /api/sessions?limit=1000. Bucket sessions by cwd.

3. Aggregate per cwd

For each working directory compute:

sessions — count.
cost — sum of the inline cost field across the bucket.
tokens — sum of input / output / cache-read / cache-write from each session's metadata usage_extras (sum the four into a total, and keep input + output as the "billable text" subtotal).
last active — the max started_at (or ended_at) in the bucket.
models — the distinct models seen.

4. Share of fleet

GET /api/pricing/cost for total_cost; show each cwd's cost as a percentage of the fleet total.

5. Ranking

Sort by cost descending by default (or count if the user asked); apply top N.

Output

Markdown table: project (cwd basename) | sessions | total tokens | cost | % of fleet | last active | models. Currency as USD to 4 decimal places; token counts with thousands separators; sort cost-descending. Add a final TOTAL row summing the columns. Only count tokens that the session metadata actually carries — if usage_extras is absent for a session, note it as excluded rather than guessing. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

---name: cwd-rollupdescription: Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.---# CWD RollupAggregate session activity per working directory (project).## InputThe user provides: **$ARGUMENTS**- Empty → roll up **all** working directories.- A path / project substring → restrict the rollup to matching cwds.- `top N` → keep only the N highest-cost (or highest-count) projects.## Data Sources| Endpoint | Returns ||----------|---------|| `GET /api/run/cwds` | the distinct working directories that have sessions — the rollup key set || `GET /api/sessions?limit=N` | session list: id, status, model, cwd, started_at, ended_at, cost, metadata (usage_extras with token counts) || `GET /api/pricing/cost` | fleet cost: total_cost, breakdown[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] — for the fleet total to compute each cwd's share |## Report Sections### 1. Key set`GET /api/run/cwds` for the canonical list of working directories. Apply the`$ARGUMENTS` filter (substring match) if one was given.### 2. Pull sessions`GET /api/sessions?limit=1000`. Bucket sessions by `cwd`.### 3. Aggregate per cwdFor each working directory compute:- **sessions** — count.- **cost** — sum of the inline `cost` field across the bucket.- **tokens** — sum of input / output / cache-read / cache-write from each session's metadata `usage_extras` (sum the four into a total, and keep input + output as the "billable text" subtotal).- **last active** — the max `started_at` (or `ended_at`) in the bucket.- **models** — the distinct models seen.### 4. Share of fleet`GET /api/pricing/cost` for `total_cost`; show each cwd's cost as a percentage of thefleet total.### 5. RankingSort by cost descending by default (or count if the user asked); apply `top N`.## OutputMarkdown table: `project (cwd basename) | sessions | total tokens | cost | % of fleet | last active | models`.Currency as USD to 4 decimal places; token counts with thousands separators; sortcost-descending. Add a final TOTAL row summing the columns. Only count tokens thatthe session metadata actually carries — if `usage_extras` is absent for a session,note it as excluded rather than guessing. If the dashboard is unreachable, tell theuser to start it with `npm start` from the repo root.

Frequently asked questions