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.
git clone --depth 1 https://github.com/vinnie357/claude-skillsnpx agentmods add commands/vinnie357/claude-skills/assessWrote 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/commands/vinnie357/claude-skills/assess)<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.
<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>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.00023 | $0.00570 |
| Opus 5 | $0.00012 | $0.00285 |
| Sonnet 5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
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 5d 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
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:
- Discovery (scoped) —
pm-discoveryinventories dependencies, external integrations, and stack/framework choices only. No routes/pages or data-model shards, no bees map. - SDLC assessment —
pm-sdlc-assessorwalks the licensing/security/supportability checklist from/pm:spec-harvest'sreferences/sdlc-checklist.md, evidencing every row. - Write —
pm-spec-writercomposes<OUTPUT_DIR>/<DATE>-sdlc-assessment.mdonly. 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. Defaultdocs/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/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.
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.
- 5d ago First seen · 39 lines · 23 tokens per session scan A 924c1bbc6de1
assess is a command published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 570 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-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.