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 skills add Enakoneschniy/claude-dev-stack --skill cds-statsgit clone --depth 1 https://github.com/Enakoneschniy/claude-dev-stackWrote 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/enakoneschniy/claude-dev-stack/cds-stats)<a href="https://agentmods.dev/skills/enakoneschniy/claude-dev-stack/cds-stats"><img src="https://agentmods.dev/badge/skills/enakoneschniy/claude-dev-stack/cds-stats/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/skills/enakoneschniy/claude-dev-stack/cds-stats"><img src="https://agentmods.dev/badge/skills/enakoneschniy/claude-dev-stack/cds-stats.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.00029 | $0.00442 |
| Opus 5.5 | $0.00012 | $0.00177 |
| Sonnet 5.5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
cds-stats 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
/cds-stats -- Project memory dashboard
Display a summary of the project's session memory and planning status.
How to execute
-
Get planning status (MCP tool):
mcp__cds__planning.status()This returns the current ROADMAP phase counts and STATE position.
-
Get session memory stats: Use Bash to call the mem-stats CLI command:
Bash("npx claude-dev-stack mem-stats")This returns: project name, session count (total + this week), observation counts by type, entity count + top entities (most referenced), last activity.
-
Combine and present: Format both outputs into a single dashboard:
Project Memory Dashboard ======================== [planning.status output -- phase progress, current position] [mem-stats output -- session count, observations, entities, last activity]The mem-stats output includes entity data per D-143/D-145:
- Total entity count
- Top entities (most referenced across observations)
Fallback
If mcp__cds__planning.status is not available, skip the planning section and show only the mem-stats CLI output.
Output format
The combined dashboard shows:
- Planning: phase progress, current position (from MCP)
- Sessions: total count + this week count
- Observations: total + breakdown by type (decision, bug, pattern, etc.)
- Entities: total count + top referenced entities
- Last activity: date of most recent session
When to use
- User asks "how's the project going"
- User asks about session/memory statistics
- User asks about top entities or most referenced concepts
- User wants to see project health overview
- User explicitly invokes
/cds-stats
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 · 65 lines · 29 tokens per session scan A 22887dc35218
cds-stats is a skill published in the GitHub repository Enakoneschniy/claude-dev-stack (5 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 442 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 skills, from other repositories
context-manager
Use when a long-running agent task needs context budgeting, checkpointing, compaction, retrieval, or capability-based model routing.
knowledge-ops
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
session-learn
Use when a completed work session should yield durable concepts, corrections, decisions, reusable patterns, and a traceable next action.
ensemble-sessionlog
Save a structured session transcript to SessionLogs with key decisions, commands, and resolutions (Codex skill for /ensemble:sessionlog).
guard
Protect Claude Code sessions from context overflow by running a background daemon that monitors session size and auto-prunes before compaction hits. Use when the user says "guard", "protect session", "context getting long", "prevent compaction", "session management", or is running agent teams that need continuous…
obsidian-untangle-knot
Offload an Obsidian hub note that too many notes link to (an in-degree tangle). The main signal of a tangle is a high in-degree (tens to hundreds of incoming links); out-degree is secondary. The skill creates sub-MOCs under the hub's existing categories and redirects incoming links from resource notes to the specific…