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/significant-change)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/significant-change"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/significant-change/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/significant-change"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/significant-change.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.00012 | $0.01140 |
| Opus 5.5 | $0.00005 | $0.00456 |
| Sonnet 5.5 | $0.00002 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
significant-change 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.
This is a copy
100% identical to significant-change — 2 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:significant-change
Analyze whether a system change qualifies as "significant" and determine the required actions.
Usage
/grc:significant-change [framework?] [change-description]
The user describes the change in the prompt or as an argument.
Arguments
- framework (optional):
fedramp,nist,fisma. Defaults tofedramp. - change-description: Free-text description of the system change (can be inline or pasted after invoking).
Examples
/grc:significant-change fedramp We are migrating our database from self-managed PostgreSQL to AWS RDS
/grc:significant-change We are adding a new API gateway in front of our application
/grc:significant-change fedramp Upgrading from RHEL 8 to RHEL 9 across all production servers
/grc:significant-change Our ISSO is leaving and we are assigning a new ISSO
/grc:significant-change Adding a new interconnection to an agency's identity provider
Behavior
When invoked:
-
Display the Data Sensitivity Notice at the top of every response (see SKILL.md Data Handling section). Users may describe system architecture details.
-
Read the appropriate reference files:
skills/grc-knowledge/audits/significant-change-criteria.mdfor the decision criteria and category definitions- Framework file from
skills/grc-knowledge/frameworks/if framework-specific parameters are needed
-
Classify the change:
- Walk through the significant change decision tree from the reference file
- Determine the change category (1-5) or determine it is not significant
- Explain the rationale for the classification
-
If significant, provide:
a. Change Category Which of the 5 categories it falls into and why.
b. Affected Control Families List the control families impacted by this change, using the control-to-change-type mapping from the reference file.
c. Required Actions — Before the Change Specific steps to take before implementing (SIA, notifications, SSP draft updates, etc.).
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 · 133 lines · 12 tokens per session scan A 58e0261b442a
significant-change is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 8mo ago), licensed MIT. It adds 12 tokens to every session and 1,140 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to significant-change, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
rgpd
Questões de RGPD e violação de dados — referência, playbook e checklist. GDPR and data-breach matters — reference, playbook and checklist.