agentmods.dev

assess

assess is a command for Claude Code from vinnie357/claude-skills. It costs 23 tokens per session (572 once invoked), scanned A, original, MIT.

A command that runs only a software-development lifecycle assessment of a prototype, covering licensing, security, and supportability.

In plain words
What is it for?
It inventories dependencies, integrations, and technology choices, checks them against a lifecycle checklist, and writes a dated assessment report.
Why use it?
It provides a focused readiness check when a full feature inventory is not needed.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is /pm:assess ../checkout-prototype --output=docs/specs/.

Part of the pm plugin — 2 skills, 3 commands, 6 agents shipped together

not rated 27repo changed 1mo ago A scan 23 tokens original MIT

Good fit It inventories dependencies, integrations, and technology choices, checks them against a lifecycle checklist, and writes a dated assessment report.

Compare 6 commands from other repositories ↓
View source ↗ vinnie357/claude-skills
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/vinnie357/claude-skills
agentmods
npx agentmods add commands/vinnie357/claude-skills/assess

Made for: Claude Code.

Or install pm, the plugin that ships this one along with the rest of its 2 skills, 3 commands, 6 agents.

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 assess

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/vinnie357/claude-skills/assess"><img src="https://agentmods.dev/badge/commands/vinnie357/claude-skills/assess.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 572 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.00023 $0.00572
Opus 5.5 $0.00009 $0.00229
Sonnet 5.5 $0.00005 $0.00114
Haiku 4.5 $0.00002 $0.00057

Measured 1mo ago against content hash a0656c7b2fa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/pm/commands/assess.md · 39 lines

What it actually says

Run only the SDLC guardrail assessment against a prototype — licensing, security, and supportability — without the full feature-harvest pipeline. Spawns the pm-lead agent scoped to a single discovery shard (integrations-deps-stack) followed by pm-sdlc-assessor and pm-spec-writer, producing one artifact.

What it does:

  1. Discovery (scoped) — pm-discovery inventories dependencies, external integrations, and stack/framework choices only. No routes/pages or data-model shards, no bees map.
  2. SDLC assessment — pm-sdlc-assessor walks the licensing/security/supportability checklist from /pm:spec-harvest's references/sdlc-checklist.md, evidencing every row.
  3. Write — pm-spec-writer composes <OUTPUT_DIR>/<DATE>-sdlc-assessment.md only. No feature inventory, no PRDs.

Arguments:

  • [path-to-prototype] — absolute or relative path to the prototype repo. When omitted, ask the user where the prototype lives before doing anything else.
  • --output=<dir> — output directory for the assessment artifact. Default docs/pm/ under the prototype root.

Examples:

/pm:assess ~/github/checkout-prototype
/pm:assess ../checkout-prototype --output=docs/specs/

Skills the lead loads (no globs — explicit names):

  • /pm:spec-harvest
  • /core:agent-loop
  • /core:anti-fabrication
  • /core:bees
  • /extras-claude-code:claude-teams

Task instructions:

Resolve [path-to-prototype] to an absolute path relative to the current working directory; if omitted, ask the operator first. Verify the path exists (test -d) — if not, stop and report. Compute DATE as today in YYYY-MM-DD. Resolve OUTPUT_DIR to an absolute path (default <path-to-prototype>/docs/pm/).

Spawn the pm-lead subagent with PROTOTYPE_ROOT=<resolved path>, MODE=assess, OUTPUT_DIR, DATE. No OPERATOR_ANSWERS clarifying pass is required for assessment-only runs — the scope is fixed to the SDLC checklist. Relay the lead's final report to the user, including the artifact path and the confidence-tag summary.

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. 1mo ago Changed a0656c7b2fa3
  2. 2mo ago First seen · 39 lines · 23 tokens per session scan A 924c1bbc6de1

Subscribe to this mod's changes

assess is a command published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 572 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-09-03.

Project managementSecurity
Related

assess compared with commands from other repositories

assess next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
assessvinnie357/claude-skillsCommand2714d agoMITA23Claude Code
checklistgithub/spec-kitCommand149ktodayMITA13Claude Code
clarifygithub/spec-kitCommand149ktodayMITA27Claude Code
specifygithub/spec-kitCommand149ktodayMITA13Claude Code
analyzegithub/spec-kitCommand149ktodayMITA26Claude Code
convergegithub/spec-kitCommand149ktodayMITA35Claude Code
implementgithub/spec-kitCommand149ktodayMITA14Claude Code