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 skills/dikamilo/dx-workflow/dx-archivenpx skills add dikamilo/dx-workflow --skill dx-archivegit clone --depth 1 https://github.com/dikamilo/dx-workflowWrote 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/skills/dikamilo/dx-workflow/dx-archive)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-archive"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-archive.svg" alt="Measured on agentmods" 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.00023 | $0.00639 |
| Opus 5 | $0.00012 | $0.00319 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
dx-archive 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-archive
Retire a finished container. One id in, one folder moved, one stamp written. No registry — the archive is just where done work lives.
Guard. If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why. Never half-move.
Resolve
The argument is one id. Find its home:
context/changes/<id>/→ it's a change.context/efforts/<id>/→ it's an effort.- Neither, or both → fail loud: print what you looked for and stop. (Already under
context/archive/? Say it's already archived.)
Effort gate — children first
An effort is done only when every child change is already archived. Before moving an effort, read its roadmap.md, and for each linked child change check for archived_at (derive it — scan the child's change.md, don't trust a checkbox). If any child is still open, list them and ask before continuing. The user may override.
Review gate — unresolved findings
For a change, check reviews/impl-review.md. If it has any finding with Resolution: PENDING, warn — "N unresolved impl-review finding(s) — /dx-review-triage impl to address them first" — and ask whether to archive anyway. The user may override.
Move and stamp
- Destination:
context/archive/<today>-<id>/where<today>isdate +%F. If it already exists, fail loud and stop. - Stamp the moved container's
change.md(oreffort.md): setstatus: archivedandarchived_at:to today's date (date +%F, same format ascreated/updated— no other field in the schema carries a finer timestamp); bumpupdated:. Leave every other field alone. For the exact schema, invokedx-referenceswith topicchange-md(a change) oreffort-md(an effort). - Move the whole folder: prefer
git mvso history follows; fall back tomv(warn) if git is unavailable. Confirm the source is gone and the destination exists — if not, print a diagnostic and stop.
Done when
The folder lives at context/archive/<today>-<id>/, its identity file reads status: archived with archived_at set, and nothing remains under the old path. Print:
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 Changed · -1 lines 22fec0b00d8e
- 5d ago First seen · 45 lines · 23 tokens per session scan A 854840be8562
dx-archive is a skill published in the GitHub repository dikamilo/dx-workflow (5 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 639 once invoked, about $0.0001 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-31.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…