Borrowing it
Nothing to install: this file belongs to techequitycloud/rad-modules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/techequitycloud/rad-modules/main/.claude/commands/sync-docs.mdgit clone --depth 1 https://github.com/techequitycloud/rad-modulesWrote 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/techequitycloud/rad-modules/sync-docs)<a href="https://agentmods.dev/commands/techequitycloud/rad-modules/sync-docs"><img src="https://agentmods.dev/badge/commands/techequitycloud/rad-modules/sync-docs/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/techequitycloud/rad-modules/sync-docs"><img src="https://agentmods.dev/badge/commands/techequitycloud/rad-modules/sync-docs.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.00000 | $0.00723 |
| Opus 5.5 | $0.00000 | $0.00289 |
| Sonnet 5.5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
sync-docs 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 26d 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.
What it actually says
Find and fix all documentation drift between the rad-modules codebase and its docs
(CLAUDE.md, README.md, SKILLS.md, AGENTS.md, per-module README.md/<Module>.md, and
docs/labs/<Module>.md).
Run every check below and apply fixes directly.
CHECK 1 — MODULE LIST
List every directory under modules/ that is a real module (has main.tf or variables.tf;
PascalCase_WithUnderscores name). Compare against:
a) The "Module Families" table in CLAUDE.md.
b) (Nothing in README.md — it is the upstream OpenTofu project README and carries no module
list. Do not add one.)
c) Any module enumeration in SKILLS.md and AGENTS.md.
Add missing modules; remove entries whose directory no longer exists. Keep the
"what it deploys" one-liners accurate.
CHECK 2 — README INPUTS/OUTPUTS TABLES
For each module, compare its README.md ## Inputs table against variables.tf and its
## Outputs table against outputs.tf (and any outputs in main.tf):
a) Every variable appears as a row with matching default and a description that matches
variables.tf verbatim minus the {{UIMeta ...}} tag.
b) Every output appears in the Outputs table.
Add missing rows, fix stale defaults/descriptions. Do the same for the ## Requirements
and ## Providers tables against versions.tf / provider.tf.
CHECK 3 — LAB GUIDE LINKS
For each module:
a) module_documentation default in variables.tf must point at that module's published
documentation — https://docs.radmodules.dev/docs/modules/<Module> (the preferred form,
used by AKS_GKE/Bank_GKE/EKS_GKE/Istio_GKE/MC_Bank_GKE) or the GitHub URL of
docs/labs/<Module>.md (still used by Container_Migration/Gemini_Enterprise/Migration_Center/VMware_Engine).
Fix only if it points at neither — especially a LAB_GUIDE.md.
b) README.md links the lab guide as ../../docs/labs/<Module>.md. Fix broken links.
c) Confirm docs/labs/<Module>.md exists; if a module has none, report it.
d) Report (do not auto-delete) any LAB_GUIDE.md found inside a module directory — that
file should not exist; the lab guide always lives under docs/labs/.
CHECK 4 — SKILL FILE ACCURACY
For each .agent/skills/*/SKILL.md, verify any file lists, module names, variable names,
or counts it states still match the codebase. Update stale references. Pay attention to
module-conventions/SKILL.md (the ten standard variables, provider patterns) and
repository-context/SKILL.md.
CHECK 5 — SCRIPT & PATH REFERENCES
Scan CLAUDE.md, AGENTS.md, README.md, and SKILLS.md for references to scripts/<name>,
rad-launcher/<name>, and workflow files. Verify each path exists; fix broken references.
After applying all fixes, run tofu fmt -recursive modules/ if any .tf changed, then
report a summary of what was updated. Do not commit unless asked.
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.
- 26d ago Changed 26bd8f6f93b1
- 1mo ago First seen · 67 lines · 0 tokens per session scan A 2c7cd08daa38
sync-docs is a command published in the GitHub repository techequitycloud/rad-modules (2 stars, last pushed yesterday), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 723 tokens. 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 commands, from other repositories
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.