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.
npx agentmods add commands/griddynamics/rosetta/security-flow-normalize-and-triagegit clone --depth 1 https://github.com/griddynamics/rosettaWrote 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/griddynamics/rosetta/security-flow-normalize-and-triage)<a href="https://agentmods.dev/commands/griddynamics/rosetta/security-flow-normalize-and-triage"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/security-flow-normalize-and-triage.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00495 |
| Opus 5 | $0.00010 | $0.00247 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
security-flow-normalize-and-triage 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 today.
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
<security_flow_normalize_and_triage>
<description_and_purpose> Convert findings losslessly, then apply independent security judgment. </description_and_purpose>
<workflow_context>
Phase 6. Requires separate executor and engineer invocations.
</workflow_context>
<phase_steps>
- Convert source records
- Correlate related evidence
- Verify material findings
- Recommend dispositions and priority </phase_steps>
- USE SKILL
subagent-directives. - USE SKILL
securityfor its normalized-finding contract. - Convert records mechanically.
- Preserve source fields byte-for-byte where representable.
- Link evidence envelopes.
- Report conversion errors; never infer missing fields.
- Update
security-flow-state.md.
- USE SKILL
subagent-directives. - USE SKILL
security. - Correlate without deleting source records.
- Seek a second signal or bounded reproduction for material high+.
- Otherwise retain high+ as unverified.
- Assign auditable dispositions.
- Recommend P0-P3 using context.
- Explain every severity uplift/downgrade separately from source severity.
- Identify shared root cause and fix strategy.
- Update
security-flow-state.md.
<validation_checklist>
- Source count and identities reconcile.
- Correlations retain every source link.
- High+ verification status is explicit.
- Dispositions and priorities have rationale. </validation_checklist>
</security_flow_normalize_and_triage>
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.
- today First seen · 63 lines · 19 tokens per session scan A 619085ef94b2
security-flow-normalize-and-triage is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 495 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
resolve-conflicts
Resolve merge conflicts on a GitHub PR by merging the base branch into the PR branch in an isolated git worktree, with JSON/markdown-aware conflict resolution.
xpoz-best-practices
Reference docs for Xpoz query syntax, pagination, field selection, platform tools, and authentication. Usage: /xpoz-best-practices.
align
Verify spec-vs-spec alignment and brevity across the intent tree. This is NOT QA — QA checks code against a spec; alignment checks whether specs are consistent with their ancestors and internally tight against the Brevity Contract. The aligner runs three passes per walk.
deploy-check
Pre-flight verification before pushing to main. Reproduces the CI gates locally so the push doesn't fail in production.
validate-fix
Validate a proposed React fix with React-Sentinel assertions or replay checks.
rclone_mkdir
Make the path if it doesn't already exist.