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/techequitycloud/rad-modules/check-conventionsgit clone --depth 1 https://github.com/techequitycloud/rad-modulesWhat 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.00000 | $0.00639 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
check-conventions 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 2d 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
Check every module under modules/ for convention drift against the binding rules in
.agent/skills/module-conventions/SKILL.md and CLAUDE.md.
rad-modules has NO shared foundation module — each module is independent. "Drift" here means a module diverging from the repo-wide conventions, not from a parent module.
Start by running the mechanical checker, then add the judgement-based checks it can't do:
python3 scripts/check_conventions.py # FAIL findings break, WARN findings inform
python3 scripts/check_conventions.py --strict # treat warnings as failures too
Summarise its output, then verify the following across all modules.
Step 1 — STANDARD VARIABLE CONSISTENCY
Collect every module's variables.tf. For the ten standard variables
(module_description, module_dependency, module_services, credit_cost,
require_credit_purchases, enable_purge, public_access, deployment_id,
resource_creator_identity, trusted_users) verify:
a) The variable is present (note the legitimate exceptions: AKS_GKE, EKS_GKE and
Migration_Center omit enable_services; Container_Migration, Migration_Center and
VMware_Engine omit trusted_users).
b) Its TYPE matches across modules (e.g. trusted_users is always list(string)).
c) resource_creator_identity default is the standard SA
("[email protected]").
d) trusted_users carries the duplicate-and-whitespace validation blocks from
AKS_GKE/variables.tf.
Report per module: ": — ".
Step 2 — UIMETA COMPLETENESS
Every variable in every module must have a {{UIMeta group=N order=M}} tag in its
description. List any variable missing it, grouped by module.
Step 3 — API ENABLEMENT INVARIANT
For every google_project_service across all modules, confirm
disable_dependent_services = false and disable_on_destroy = false, and that none use
lifecycle { prevent_destroy = true }. Report any violation — this is a hard rule.
Step 4 — LICENSE HEADERS & SYMLINKS
a) Report any .tf file missing the Apache 2.0 header. b) Report any symlink found inside a module directory (modules must never share files).
Output
Group findings by module; skip modules with none. If everything is consistent, say: "All modules are consistent with the repo conventions."
If asked to FIX drift: for a missing standard variable, copy the complete variable block
(description with its {{UIMeta}} tag, type, default, validations) from a module that has it
correct (prefer AKS_GKE for the standard ten), inserting it in the right SECTION/order.
Never invent a hardcoded credential default. After fixing, run
tofu fmt -recursive modules/ and re-run the checker.
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.
- 2d ago First seen · 69 lines · 0 tokens per session scan A d037bbcb8e1d
check-conventions is a command published in the GitHub repository techequitycloud/rad-modules (2 stars, last pushed 8d ago), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 639 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.