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-status)<a href="https://agentmods.dev/commands/sivan757/dsh-agent-plugins-market/modernize-status"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-status/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-status"><img src="https://agentmods.dev/badge/commands/sivan757/dsh-agent-plugins-market/modernize-status.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.00020 | $0.00798 |
| Opus 5.5 | $0.00008 | $0.00319 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
modernize-status 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
94% identical to modernize-status — 75 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report where the modernization of $1 stands, in one screen. This is a
read-only command — inspect, never modify.
1 — Artifact inventory
Check analysis/$1/ and modernized/$1*/ and build a table — one row per
workflow stage, with the artifact's presence and modification time:
| Stage | Artifacts |
|---|---|
| preflight | PREFLIGHT.md (note whether the Check 0 human answers and the Check 6 scope-boundary finding are present) |
| assess | ASSESSMENT.md, ARCHITECTURE.mmd |
| map | topology.json, TOPOLOGY.html, *.mmd, extract_topology.* |
| extract-rules | BUSINESS_RULES.md, DATA_OBJECTS.md |
| brief | MODERNIZATION_BRIEF.md (note whether the approval block is signed) |
| harden | SECURITY_FINDINGS.md, security_remediation.patch |
| uplift | DELTA_CATALOG.md, BASELINE.md, PLAYBOOK.md (no playbook = the pilot hasn't happened yet — the fan-out must not); modernized/$1-uplifted/UPLIFT_NOTES.md (note per-unit: builds on target? baseline reproduced?) |
| transform | each modernized/$1/<module>/ dir — note test presence and whether TRANSFORMATION_NOTES.md exists |
| reimagine | modernized/$1-reimagined/ — note per-service acceptance tests and the AGENTS.md handoff (reimagine's completion markers; it does NOT write TRANSFORMATION_NOTES.md) |
2 — Staleness
Flag any artifact older than an upstream artifact it derives from:
MODERNIZATION_BRIEF.mdolder thanASSESSMENT.md,topology.json, orBUSINESS_RULES.md→ the brief no longer reflects discovery; recommend re-running/modernize-brief.MODERNIZATION_BRIEF.mdfor a same-stack uplift plan that is older thanDELTA_CATALOG.md— or that has no catalog at all — → the phase order was decided before (or without) the version deltas that determine it; recommend re-running/modernize-brief.TOPOLOGY.htmlolder thantopology.json→ re-run the injection step from/modernize-map.- Any
TRANSFORMATION_NOTES.mdolder thanBUSINESS_RULES.md→ the module may not implement the latest rule set; list which.
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 · 61 lines · 20 tokens per session scan A 61741d084609
modernize-status is a command published in the GitHub repository Sivan757/dsh-agent-plugins-market (13 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 798 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to modernize-status, differing in 75 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.