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-readinessgit 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-readiness)<a href="https://agentmods.dev/commands/griddynamics/rosetta/security-flow-readiness"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/security-flow-readiness.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.00013 | $0.00463 |
| Opus 5 | $0.00006 | $0.00231 |
| Sonnet 5 | $0.00003 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
security-flow-readiness 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_readiness>
<description_and_purpose> Establish minimal context and gate secret-bearing files before model source ingestion. </description_and_purpose>
<workflow_context>
Phase 1. Mandatory executor; bounded metadata and commands only.
</workflow_context>
<phase_steps>
- Inventory request metadata
- Inventory available tools
- Run filename-only secret gate
- Return gate decision </phase_steps>
<execute_readiness step="1.1" subagent="executor" role="Bounded readiness and secret-gate operator" subagent_required_model="Claude Haiku 4.5, GPT-5.6 Terra, Gemini 3.7 Flash, GPT-5.6 Luna">
- USE SKILL
subagent-directives. - USE SKILL
security. - USE SKILL
sensitive-data. - Read request metadata only: target names, paths, environment labels, requested review type.
- List installed/reachable tools without installation, authentication, or network calls.
- Prefer an approved filename-only secret scanner.
- Otherwise USE SKILL
securityfor its filename-only fallback. - Return affected filenames only, never matches or content.
- Classify environment from approved metadata, not file values.
- Update
security-flow-state.md.
</execute_readiness>
Return exactly one token:
- No candidate files: PASS.
- DEV/QA envs only: NEEDS-HITL; recommend exclusions.
- Above-QA or ambiguous: STOP-HIGH-RISK.
- Scanner unusable or scanner exit 2: STOP-SCANNER-UNUSABLE; do not ingest source.
<validation_checklist>
- No source content entered agent context.
- Output contains filenames and metadata only.
- Tool inventory records availability, not assumptions.
- Gate decision matches the strictest environment. </validation_checklist>
</security_flow_readiness>
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 · 62 lines · 13 tokens per session scan A 83f801f8e789
security-flow-readiness is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 463 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.