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/nathanimphilipos/synergos-grcWrote 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/nathanimphilipos/synergos-grc/rev5-transition)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/rev5-transition"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/rev5-transition/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/nathanimphilipos/synergos-grc/rev5-transition"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/rev5-transition.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.00015 | $0.01361 |
| Opus 5 | $0.00008 | $0.00681 |
| Sonnet 5 | $0.00003 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
rev5-transition 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 12d 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.
This is a copy
100% identical to rev5-transition — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:rev5-transition
Provide NIST 800-53 Rev 4 to Rev 5 transition guidance — control mapping, gap analysis, and migration steps.
Usage
/grc:rev5-transition [action] [control-or-family?]
Arguments
-
action: What to do. Accepts:
lookup(default): Look up what changed for a specific Rev 4 control in Rev 5gaps: Show new controls added in Rev 5 that need implementationwithdrawn: Show controls withdrawn in Rev 5 and where they wentbaseline-changes: Show what was added/removed from baselines between revisionschecklist: Full transition checklist with steps and sequence
-
control-or-family (optional): A Rev 4 control ID (e.g.,
ac-2,sa-12) or family (e.g.,ac,sa) to look up
Examples
/grc:rev5-transition lookup sa-12
/grc:rev5-transition lookup ac-2
/grc:rev5-transition gaps
/grc:rev5-transition gaps sr
/grc:rev5-transition withdrawn
/grc:rev5-transition baseline-changes moderate
/grc:rev5-transition checklist
Behavior
When invoked:
-
No redaction reminder needed — this is a pure reference command comparing framework revisions. No user content is processed.
-
Read the appropriate reference files:
skills/grc-knowledge/frameworks/nist-rev4-to-rev5.mdfor the transition mappingskills/grc-knowledge/frameworks/nist-800-53.mdfor Rev 5 control detailsskills/grc-knowledge/frameworks/fedramp.mdfor FedRAMP-specific transition context
-
For
lookupaction: Given a Rev 4 control or family:- Show what changed between Rev 4 and Rev 5
- If the control was withdrawn, show where the requirements moved
- If the control was modified, highlight the key differences
- If new enhancements were added, list them
- Provide migration action for the SSP narrative
-
For
gapsaction: Show all controls that are new in Rev 5 (didn't exist in Rev 4):- New PT family controls
- New SR family controls
- New controls added to existing families
- For each: baseline assignment, brief description, implementation effort estimate
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.
- 12d ago First seen · 170 lines · 15 tokens per session scan A a85e254061eb
rev5-transition is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 1,361 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to rev5-transition, differing in 0 lines, and is treated as a copy.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.