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.
git clone --depth 1 https://github.com/Sivan757/dsh-agent-plugins-marketWrote 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/sivan757/dsh-agent-plugins-market/modernize-assess)<a href="https://agentmods.dev/commands/sivan757/dsh-agent-plugins-market/modernize-assess"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-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/sivan757/dsh-agent-plugins-market/modernize-assess"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-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.00018 | $0.02866 |
| Opus 5.5 | $0.00007 | $0.01146 |
| Sonnet 5.5 | $0.00004 | $0.00573 |
| Haiku 4.5 | $0.00002 | $0.00287 |
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 today.
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 — 306 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 — 239 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
Read ${PLUGIN_ROOT}/workflows/portfolio-assess.meta.json and
${PLUGIN_ROOT}/workflows/portfolio-assess.js, then pass the meta file's
contents as meta and the script file's contents (the JavaScript body, with
no export const meta line) as script:
workflow({
meta: <contents of ${PLUGIN_ROOT}/workflows/portfolio-assess.meta.json>,
script: <contents of ${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.
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.
- today First seen · 239 lines · 18 tokens per session scan A f1970773a79b
modernize-assess is a command published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 2,866 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to modernize-assess, differing in 306 lines, and is treated as a copy.
Other commands, from other repositories
memory-report
Calibration + inventory check of your causal memory (prediction ledger accuracy, what you know).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.