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/ssp-section)<a href="https://agentmods.dev/commands/nathanimphilipos/synergos-grc/ssp-section"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/ssp-section/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/ssp-section"><img src="https://agentmods.dev/badge/commands/nathanimphilipos/synergos-grc/ssp-section.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.00005 | $0.01016 |
| Opus 5 | $0.00003 | $0.00508 |
| Sonnet 5 | $0.00001 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
ssp-section 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 9d 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 ssp-section — 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grc:ssp-section
Draft SSP (System Security Plan) control family descriptions.
Usage
/grc:ssp-section [framework] [control-family]
Arguments
- framework: The compliance framework. Primarily
nist,fedramp, orfisma(SSP is an RMF artifact). Also supportscmmcfor NIST 800-171 security plans. - control-family: The control family ID or name (e.g.,
ac,access-control,ir,incident-response).
Examples
/grc:ssp-section fedramp ac
/grc:ssp-section nist ir
/grc:ssp-section fedramp ia
/grc:ssp-section cmmc access-control
/grc:ssp-section fedramp sc
Behavior
When invoked:
-
Identify the framework, baseline, and control family from arguments. Default to FedRAMP Moderate if no baseline specified.
-
Read the OSCAL family JSON for the complete control list and parameter definitions (use the Read tool — do NOT use Bash, Python, or jq to extract data):
- For
nist: readskills/grc-knowledge/oscal/nist-800-53-rev5/{family}.json - For
fedramp: readskills/grc-knowledge/oscal/fedramp-moderate-rev5/{family}.json - Extract all controls, enhancements, parameters (ODPs), and statement parts from the OSCAL data
- Use parameter values from the OSCAL data to populate FedRAMP-specific ODP values in narratives
- Read
.parts[] | select(.name == "assessment-objective")to ensure the narrative addresses every testable objective — each leaf objective's.prosedescribes what an assessor will verify, so the narrative must cover it - ID normalization:
AC-2→ac-2,AC-2(1)→ac-2.1
- For
-
Read the framework reference file from
skills/grc-knowledge/frameworks/for additional narrative context, audit expectations, and cross-framework guidance. -
For each control in the family (at the appropriate baseline), draft SSP narrative language following the standard format:
SSP Narrative Structure (per control):
- What: The control objective and what is being implemented
- Who: Responsible roles and teams
- How: Implementation details — mechanisms, tools, processes
- When: Frequency of the activity (if applicable)
- Where: System boundary applicability
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.
- 9d ago First seen · 111 lines · 5 tokens per session scan A 0ebe987bf137
ssp-section is a command published in the GitHub repository nathanimphilipos/synergos-grc (5 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 1,016 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 ssp-section, 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.