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.
git clone --depth 1 https://github.com/grcengineering/companionWrote 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/grcengineering/companion/translate)<a href="https://agentmods.dev/commands/grcengineering/companion/translate"><img src="https://agentmods.dev/badge/commands/grcengineering/companion/translate/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/grcengineering/companion/translate"><img src="https://agentmods.dev/badge/commands/grcengineering/companion/translate.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.00014 | $0.00148 |
| Opus 5.5 | $0.00006 | $0.00059 |
| Sonnet 5.5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
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 1mo 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
Cross-Domain Translator Command
Use when the learner needs a different lens.
Flow
- Name the GRC stuck point.
- Pick one adjacent-domain pattern.
- Explain the native pattern.
- Translate it into GRC.
- Name where the metaphor breaks.
- Ask the learner to apply the lens to their situation.
Boundary
The metaphor is for learning. It must not become operational advice.
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.
- 1mo ago First seen · 28 lines · 14 tokens per session scan A fe0657727d16
translate is a command published in the GitHub repository grcengineering/companion (34 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 148 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
evidence-examples
Get evidence examples for FedRAMP compliance.
list-ksi
List Key Security Indicators from FedRAMP.
search
Search FedRAMP documentation for compliance guidance.
list-documents
List all FedRAMP FRMR documents.
Ingest Legacy SSP
Run the end-to-end legacy SSP import process: extract source material, create source traceability, bootstrap a Trestle workspace, map content, validate OSCAL, and report unmapped items.
Fetch OSCAL Baseline
Download the NIST SP 800-53 Rev 5 catalog and a FedRAMP Rev 5 baseline profile, then import both into a Compliance Trestle workspace for real-baseline SSP drafting.