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 skills add dikamilo/dx-workflow --skill dx-standards-discovergit 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-standards-discover)<a href="https://agentmods.dev/skills/dikamilo/dx-workflow/dx-standards-discover"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-standards-discover/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/skills/dikamilo/dx-workflow/dx-standards-discover"><img src="https://agentmods.dev/badge/skills/dikamilo/dx-workflow/dx-standards-discover.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.00027 | $0.00649 |
| Opus 5 | $0.00014 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
dx-standards-discover 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 8d ago.
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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-standards-discover
Mine this project's actual conventions — from tooling, recurring code, and existing docs — and write them as prescriptive standard files under context/standards/. Record only what the codebase genuinely evidences: no inherited opinions, no aspirational rules. This fills the frontend/, backend/, testing/ layers dx-init left empty.
Guard. context/standards/{frontend,backend,testing}/ must exist. If it is missing, tell the user to run /dx-init first. Never overwrite global/ — dx-init seeded it; only append a global file if a genuinely new project-wide rule surfaces that none of the seeds cover. With --from=PATH, mine that external codebase instead of the working tree.
1 — Read the fixed sources
Read the config that already encodes rules: linter + formatter configs, tsconfig/compiler settings, CI workflows, pre-commit hooks, package.json/build scripts, .editorconfig. Then read READMEs and any docs/ that state conventions. These are the strongest evidence — a rule in a linter config is enforced, not wished-for. Read foundation/glossary.md for naming (a one-line habit — no section).
2 — Mine code patterns by layer
Fan out one built-in Explore subagent per layer present (frontend, backend, testing). Each reports the recurring patterns actually in the code — component/module structure, API shape and error handling, state and data access, test structure and naming, file layout. A convention counts only when it recurs across several files; one example is not a standard. Skip any layer the project doesn't have.
3 — Write the standard files
Group findings by layer + topic into concise, prescriptive files (~20–30 lines each) — e.g. frontend/components.md, backend/api.md, testing/test-writing.md. Match the seeded style: a ## per rule, "do this" phrasing, a short example only when it clarifies. Every rule must trace to something you saw — name the config or pattern in a few words, and drop anything you can't back. Where config and code disagree, follow the enforced config and flag the drift as a lesson candidate — don't average the two.
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.
- 8d ago First seen · 32 lines · 27 tokens per session scan A a9ec66e2f69e
dx-standards-discover is a skill published in the GitHub repository dikamilo/dx-workflow (5 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 649 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…