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 agentmods add commands/thevibeworks/claude-code-docs/modernize-assessgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWhat 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 | $0.00018 | $0.02781 |
| Opus 5 | $0.00009 | $0.01391 |
| Sonnet 5 | $0.00004 | $0.00556 |
| Haiku 4.5 | $0.00002 | $0.00278 |
Grade A, and why
modernize-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 yesterday.
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.
This is a copy
100% identical to modernize-assess — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mode select. If $ARGUMENTS starts with --portfolio, run Portfolio
mode against the directory that follows. Otherwise run Single-system
mode against the system dir. Parse flags positionally-independently:
--show-secrets may appear before or after the system dir — the system
dir is the first non-flag token.
Portfolio mode (--portfolio <parent-dir>)
Sweep every immediate subdirectory of the parent dir and produce a heat-map a steering committee can use to sequence a multi-year program.
Preferred — Workflow orchestration. If the Workflow tool is available in this session (this command invocation is your authorization), enumerate the immediate subdirectories first — the workflow script has no filesystem access — then launch one survey agent per system, all independent:
ls -d <parent-dir>/*/ | xargs -n1 basename # bare subdir names, not paths
Workflow({
scriptPath: "${CLAUDE_PLUGIN_ROOT}/workflows/portfolio-assess.js",
args: { parentDir: "<parent-dir>", systems: ["<sub1>", "<sub2>", ...] }
})
This is one agent per system (a 30-system estate = 30 agents — tell the user
the count before launching; the runtime queues them against its concurrency
cap). Each agent returns a structured metrics row and the workflow computes
COCOMO-II uniformly in code, so every row uses the identical formula. On
return, render rows (plus an "unmeasured" marker row for anything in
unmeasured) into the Step P4 heat-map, add the sequencing recommendation
yourself, and skip Steps P1–P3. For very long sweeps, note the workflow's
runId — if the session dies mid-sweep, relaunch with resumeFromRunId and
completed systems return instantly from cache.
Fallback (no Workflow tool): run Steps P1–P3 per system yourself, then P4.
Step P1 — Per-system metrics
For each subdirectory <sys>:
cloc --quiet --csv <parent>/<sys> # LOC by language
lizard -s cyclomatic_complexity <parent>/<sys> 2>/dev/null | tail -1
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.
- yesterday First seen · 233 lines · 18 tokens per session scan A 28bdeb5de2c9
modernize-assess is a command published in the GitHub repository thevibeworks/claude-code-docs (38 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 2,781 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to modernize-assess, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
reconcile
Check developer guides for documentation drift against recent code changes.
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
audit
Re-audit accepted ADRs against the codebase — verify each still holds, then amend, supersede, or deprecate the ones that don't.
curate
Curate research files — inventory by type, identify stale/superseded candidates, update frontmatter status.
create
Create a new Architecture Decision Record.
from-spec
Extract Architecture Decision Records from a completed spec.