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-harden)<a href="https://agentmods.dev/commands/sivan757/dsh-agent-plugins-market/modernize-harden"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-harden/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-harden"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-harden.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.00021 | $0.01876 |
| Opus 5.5 | $0.00008 | $0.00750 |
| Sonnet 5.5 | $0.00004 | $0.00375 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
modernize-harden 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
95% identical to modernize-harden — 226 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a security hardening pass on the legacy system: find
vulnerabilities, rank them, and produce a reviewable patch for the
critical ones. Parse arguments flag-independently: the system dir
(referred to as $1 below) is the first non-flag token in $ARGUMENTS;
--show-secrets may appear anywhere.
This command never edits legacy/ — it writes findings and a proposed patch
to analysis/$1/. The user reviews and applies (or not).
Step 0 — Secrets quarantine setup
Findings files get shared, committed, and pasted into decks — discovered credential values must never land in them. Before any scanning:
- Ensure
analysis/.gitignoreexists and contains the linesSECRETS.local.mdand*.local.patch. Create the file or append the missing lines. - If the project is a git repo, verify with
git check-ignore -q analysis/$1/SECRETS.local.md— if that exits non-zero, fix the ignore rule before proceeding. Do not write any findings until this check passes. - If there is no git repo (check for
.svn/.hg/CVStoo — a.gitignoreprotects nothing under another VCS): refuse--show-secrets, and writeSECRETS.local.mdand any.local.patchfile to~/.modernize/$1/instead of the project tree, telling the user where they went and why.
All secret values in every shareable artifact this command produces are
masked (AKIA****, password=****) and cited by file:line. Raw
values may appear in exactly two places, both gitignored: the
*.local.patch remediation hunks (unavoidably — see Remediate) and, only
with --show-secrets, SECRETS.local.md. Never in SECURITY_FINDINGS.md
or patch commentary.
Scan
Preferred — workflow orchestration. If the workflow tool is available in this session, use it (this command invocation is your authorization):
Read ${PLUGIN_ROOT}/workflows/harden-scan.meta.json and
${PLUGIN_ROOT}/workflows/harden-scan.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:
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 · 161 lines · 21 tokens per session scan A 2dc161c618e0
modernize-harden is a command published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,876 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to modernize-harden, differing in 226 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.