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/ucsandman/dashclaw/dashclaw-retire-legacygit clone --depth 1 https://github.com/ucsandman/DashClawWhat 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.00042 | $0.01509 |
| Opus 5 | $0.00021 | $0.00754 |
| Sonnet 5 | $0.00008 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
dashclaw-retire-legacy 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal: retire the legacy SDK without breaking anyone
dashclaw/legacy is a published npm subpath (./legacy in sdk/package.json exports + files; it ships in the tarball). External integrations can import 'dashclaw/legacy' today, so it cannot be silently deleted — every release republishes the npm package at the unified version, so a delete would land in the next patch and break those users with no major signal. Retirement is therefore two milestones:
deprecate(now, default) — announce the retirement, keep it working.remove(later, at the v5 major) — delete it as a breaking change.
$ARGUMENTS selects the phase (default deprecate). This command authorizes the Workflow tool (legacy-sdk-deprecation-sweep, mode = the phase).
Phase: deprecate (run this now)
-
Run the workflow in deprecate mode:
Workflow({ name: "legacy-sdk-deprecation-sweep", args: { mode: "deprecate", removalVersion: "5.0.0" } }). It audits every livedashclaw/legacyreference, then in parallel: adds a one-time runtime deprecationconsole.warn(opt-out viaDASHCLAW_SUPPRESS_LEGACY_WARNING=1) +@deprecated, marks every doc/parity surface "removed in v5.0.0", reconciles the drifting method counts (178/187/224), repoints the doc example onto canonical, edits the reference sources (not mirrors), closes the.organismsplit-the-file backlog, and adds a CHANGELOG### Deprecatedentry. -
Trust nothing — re-read the diffs. Confirm the deprecation markers landed AND, critically, that
sdk/legacy/and the./legacyexport +filesentry are UNTOUCHED — deprecate must not remove the published contract. Aconsole.warnis the only behavior change to the legacy code itself. -
Prove the export still works:
npm pack --dry-run(insidesdk/) must still listlegacy/dashclaw-v1.js+legacy/index-v1.cjs, and the two legacy regression tests must still pass (aconsole.warndoesn't fail them). -
Mirror the reference sources:
npm run bundles:refresh(the deprecation edits touchedpublic/downloads/dashclaw-governance/references/*.md), thengit statusto see what propagated.
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 · 62 lines · 42 tokens per session scan A f42e6865cc77
dashclaw-retire-legacy is a command published in the GitHub repository ucsandman/DashClaw (296 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,509 once invoked, about $0.0002 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-30.
Other commands, from other repositories
code-review
Provide a code review for the given pull request.
echo
This is a placeholder command definition for plugin framework tests.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.
create-issue
Open a GitHub issue on the Ion engine repo for a bug or feature request derived from the current conversation, with consumer project details scrubbed.
squash
Rebuild a feature branch into clean conventional commits while preserving its exact final tracked tree.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.