translate

A command for explaining a governance, risk, and compliance (GRC) problem through a pattern from another field. It also requires explaining where that comparison stops being useful.

In plain words
What is it for?
Translating an identified GRC sticking point into a learning example, explaining the original pattern, and applying the comparison to a situation.
Why use it?
It offers learners a different way to understand a difficult GRC idea while keeping the comparison from being mistaken for operational advice.

Command

Install

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.

agentmods
npx agentmods add commands/grcengineering/companion/translate
Clone the repo
git clone --depth 1 https://github.com/grcengineering/companion
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 148 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00148
Opus 5 $0.00007 $0.00074
Sonnet 5 $0.00003 $0.00030
Haiku 4.5 $0.00001 $0.00015

Measured 2d ago against content hash fe0657727d16, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

translate 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.

commands/translate.md · 28 lines

What it actually says

Cross-Domain Translator Command

Use when the learner needs a different lens.

Flow

  1. Name the GRC stuck point.
  2. Pick one adjacent-domain pattern.
  3. Explain the native pattern.
  4. Translate it into GRC.
  5. Name where the metaphor breaks.
  6. Ask the learner to apply the lens to their situation.

Boundary

The metaphor is for learning. It must not become operational advice.

Changes

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.

  1. 2d ago First seen · 28 lines · 14 tokens per session scan A fe0657727d16

Subscribe to this mod's changes

translate is a command published in the GitHub repository grcengineering/companion (32 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 148 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-30.