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/boundary-guidance)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/boundary-guidance"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/boundary-guidance/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/boundary-guidance"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/boundary-guidance.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.00004 | $0.01143 |
| Opus 5 | $0.00002 | $0.00571 |
| Sonnet 5 | $0.00001 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
boundary-guidance 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 11d 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 boundary-guidance — 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:boundary-guidance
Provide guidance on authorization boundary definition based on system architecture.
Usage
/grc:boundary-guidance [framework?] [service-model?]
The user can optionally describe their architecture for tailored guidance.
Arguments
- framework (optional):
fedramp,nist,fisma. Defaults tofedramp. - service-model (optional):
iaas,paas,saas. Helps tailor boundary patterns.
Examples
/grc:boundary-guidance fedramp saas
/grc:boundary-guidance fedramp iaas
/grc:boundary-guidance fedramp
/grc:boundary-guidance We have a SaaS app on AWS with RDS, ECS, S3, CloudFront, and a VPN connection to an agency
Behavior
When invoked:
-
Display the Data Sensitivity Notice if the user describes their specific architecture (see SKILL.md Data Handling section). If only a generic service model is specified, the notice is not needed.
-
Read the appropriate reference files:
skills/grc-knowledge/audits/boundary-guidance.mdfor boundary patterns, common mistakes, and diagram requirementsskills/grc-knowledge/audits/control-inheritance.mdfor inheritance context- Framework file if framework-specific requirements apply
-
If the user describes their architecture, provide tailored guidance:
a. Boundary Recommendation
- Which components should be inside the boundary
- Which components should be outside (with interconnection documentation)
- Gray areas that need a decision, with pros/cons of each option
b. Diagram Requirements
- What the authorization boundary diagram must show
- What the network architecture diagram must show
- What the data flow diagram must show
c. Interconnection Inventory
- External connections that cross the boundary
- What each interconnection needs (ISA, ports/protocols, security measures)
d. Common Mistakes for This Architecture
- Specific boundary mistakes relevant to the described architecture
- How the 3PAO is likely to challenge the boundary
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.
- 11d ago First seen · 151 lines · 4 tokens per session scan A 1413955f8d4e
boundary-guidance is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 1,143 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to boundary-guidance, differing in 0 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.
voice-compliance
Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.