session

session is a command for Claude Code from pwdev-solucoes/pwdev-claude-marketplace. It costs 8 tokens per session (846 once invoked), scanned A, original, Apache-2.0.

A command for viewing the current software project status or continuing a previous work session. It reads saved planning, roadmap, execution, review, and verification files.

In plain words
What is it for?
Use it to request a status report or resume a session by checking project state, plans, summaries, reviews, and verification results.
Why use it?
It shows what has already been done and where the project currently stands, making it easier to continue work with the existing context.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the pwdev-code plugin — 2 skills, 22 commands, 8 agents, 6 hooks shipped together

Good fit Use it to request a status report or resume a session by checking project state, plans, summaries, reviews, and verification results.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace
Claude Code
/plugin install pwdev-code

Made for: Claude Code.

Or install pwdev-code, the plugin that ships this one along with the rest of its 2 skills, 22 commands, 8 agents, 6 hooks.

Wrote 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.

agentmods badge for session

README.md
[![agentmods](https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/session/github.svg)](https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/session)
Your own site
<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/session"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/session/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.

agentmods 80×15 button for session

Your own site · 80×15
<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/session"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.00846
Opus 5 $0.00004 $0.00423
Sonnet 5 $0.00002 $0.00169
Haiku 4.5 $0.00001 $0.00085

Measured 9d ago against content hash 1f52afa18162, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

session 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 9d 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.

plugins/pwdev-code/commands/session.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/pwdev-code:session — Session Management

Role

Utility agent for session state: displays current project status and progress, or resumes a previous session by reading persisted state.

Input

$ARGUMENTS: subcommand (optional).

  • (empty) → show status report (default)
  • resume → resume previous session

Procedure

STEP 0 — Language

Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from .planning/config.json; ask only if unset).

STEP 1 — Route Subcommand

Route on $1:

  • resume → go to STEP 3
  • empty → go to STEP 2 (Status Report)

STEP 2 — Status Report (default)

Read and present the current state:

cat .planning/state.md 2>/dev/null || echo "❌ state.md not found. No active project."
cat .planning/product/roadmap/ROADMAP.md 2>/dev/null
ls .planning/phases/*/plans/*.md 2>/dev/null
ls .planning/phases/*/execution/*-summary.md 2>/dev/null
ls .planning/phases/*/review/code-review.md 2>/dev/null
ls .planning/phases/*/review/qa-report.md 2>/dev/null
ls .planning/phases/*/verify/verify.md 2>/dev/null
ls .planning/quick/ 2>/dev/null

Present:

## 📊 Project Status

**Current phase:** [DISCOVER | DESIGN | PLAN | EXECUTE | REVIEW | VERIFY]
**Current plan:** [phase-slug/PP] | **Current task:** [phase-slug/PP-TT]
**Status:** [in progress | awaiting approval | verifying | blocked]

### Progress
| Plan | Tasks | Completed | Status |
|---|---|---|---|
| 01-01 | 3 | 3/3 | ✅ |
| 01-02 | 3 | 1/3 | 🔄 |

### Wave Map
[Wave 1: ✅ | Wave 2: 🔄 | Wave 3: ⏳]

### Blockers
[None | list]

### Memory
[N active (D decisions / L lessons / C conventions) — from .planning/memory/MEMORY.md]

### Next action
👉 [recommended command]

STEP 3 — Resume Session

STEP 3.1 — Read persisted state

cat .planning/state.md
cat .planning/product/roadmap/ROADMAP.md 2>/dev/null
ls -la .planning/phases/ 2>/dev/null

STEP 3.2 — Identify resumption point

  • Last completed phase
  • Last completed task
  • Next pending action
  • Registered blockers

Read the full file on GitHub · 121 lines

Changes

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.

  1. 9d ago First seen · 121 lines · 8 tokens per session scan A 1f52afa18162

Subscribe to this mod's changes

session is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 8 tokens to every session and 846 once invoked, about $0.0000 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-08-31.