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/NVZver/claude-marketplacenpx agentmods add skills/nvzver/claude-marketplace/checkWrote 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/nvzver/claude-marketplace/check)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/check"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/check/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/nvzver/claude-marketplace/check"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/check.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.00096 | $0.01208 |
| Opus 5 | $0.00048 | $0.00604 |
| Sonnet 5 | $0.00019 | $0.00242 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
check 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace. On load, print first:
=============== [manager/skills/check/SKILL.md] [manager] ===============
Check
Check the roadmap for hygiene issues — stale rows, missing pitches, status/branch mismatches — and apply the fixes the user approves. Runs inline in the invoking context; no agent dispatch. The five hint classes are derived deterministically by scripts/roadmap-query.sh hygiene, so the only model work is judgment over the script's hints — which does not need a fresh context (../../../.lsa/standards/code.md §Dispatch efficiency: "Everything else — spec authoring, shaping, decomposition, recommendation, review, cited lookup — runs inline."). The scan conditions themselves stay canon in ../../agents/project-manager.md Steps 6-7, which still run there when hygiene rides along with Mode 1 sequencing.
Goal
Keep the roadmap honest — flag rows whose observable state contradicts their status and apply the corrections the user approves — without the user manually auditing the roadmap, and without paying a fresh agent context to read a script's output.
Input
- None required. The roadmap is the entry point; ambient state (roadmap, pitches, branches, specs) is read on demand.
Steps
-
Get the deterministic hints. Run
bash scripts/roadmap-query.sh hygiene— it emits all five hint classes (missing-pitch, backlog-but-branch, stale-in-progress, merged-not-shipped, no-artifacts) from the ledger + git with zero model tokens and no whole-file read. Only if it exits non-zero fall through to a model-side read of${specs_root}/roadmap.yaml. Observable result: the script's hint list quoted, or an observable fall-through note. -
Confirm each hint before proposing it. The hints are input, not verdicts (
../../agents/project-manager.mdStep 6). Confirm each against what the roadmap row and any linked pitch actually say; drop hints the context explains away; respect the recency boundary — a class-5 hint means "nothing was ever created for this slug", never "this item went stale". Observable result: a confirmed finding list, or the explicit statement that the roadmap is clean.
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.
- 9d ago First seen · 63 lines · 96 tokens per session scan A 8cd29cf20be6
check is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 15d ago), licensed MIT. It adds 96 tokens to every session and 1,208 once invoked, about $0.0005 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.
Other skills, from other repositories
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
predictable-revenue
Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM). Use when the user mentions "outbound sales", "Cold Calling 2.0", "cold email sequences", "sales pipeline", "SDR process", "sales development", "build an outbound sales team", or "fill my pipeline". Also trigger when setting up a B2B…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
foreman
The one entrance to Foreman — say what you want in plain language and this routes it. Covers the six things Foreman does to a project: add work, show status, correct work, check the roadmap, pick work, or reconcile and pick. It owns no flow of its own; each intent is handed to the skill that already implements it, so…
missive
Invoke only when spawning a quest from a GitHub issue reference. Fetches GitHub issue context for quest spawning. Parses issue references, retrieves structured data via gh, and produces branch suggestions and PR keywords. Used standalone or as input to quest orchestration.