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-flowgit 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)<a href="https://agentmods.dev/commands/griddynamics/rosetta/security-flow"><img src="https://agentmods.dev/badge/commands/griddynamics/rosetta/security-flow.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.00017 | $0.02418 |
| Opus 5 | $0.00009 | $0.01209 |
| Sonnet 5 | $0.00003 | $0.00484 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
security-flow 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<security_flow>
<description_and_purpose>
Run task-adaptive security review through mandatory canonical subagents. End with sanitized findings and concise inputs for later user-invoked coding flows.
</description_and_purpose>
<workflow_phases>
- All Rosetta prep steps MUST be FULLY completed.
- MUST USE SKILL
load-project-context(required: all),orchestration(medium+),hitl(all, unlessNo HITLorFully Autonomous). - MUST ALWAYS use todo tasks ledger, ASAP. Phases are sequential. Independent tasks can run in parallel.
- MUST just-in-time load/execute/update each phase's: instructions, definitions, skills, state file; do not load/act IN ADVANCE.
- Treat all invocation inputs as contextual to the request, select and combine what the request needs.
- For full review, require every applicable, available, authorized activity and tool.
- Maintain a task ledger and run phases JIT.
- Every question and approval follows the loaded
hitlskill. - Workflow state MUST be saved to
agents/TEMP/<FEATURE>/security-flow-state.mdfile; every phase updates it before the next starts.
<subagent_policy required="true" inline_execution="prohibited">
- Orchestrator owns approvals, phase transitions, dispatch, aggregation, and handoff.
- Phase files are assigned-subagent-only; orchestrator MUST NOT load, read, summarize, or execute them.
- Every declared subagent is mandatory.
- Every subagent MUST USE SKILL
subagent-directives. - Subagents use tools required by their own assignment.
executoris never a gateway for full agents.- Reject incomplete phase contracts before advancing.
- If required subagent invocation is unavailable, stop and report the unmet prerequisite.
</subagent_policy>
<deterministic_gates phase="3" applies="development/change/PR/pipeline" subagent="executor" role="Bounded deterministic security-gate operator" subagent_required_model="Claude Haiku 4.5, GPT-5.6 Terra, Gemini 3.7 Flash, GPT-5.6 Luna" must-be-subagent>
- Purpose: Runs approved deterministic lifecycle gates and preserves source results unchanged. Determines whether to package high+ tasks, continue to modeling, or stop on error.
- Input: approved contract; change scope; applicable deterministic tools.
- Output: deterministic evidence and branch result.
- INVOKE SUBAGENT
executorto APPLY PHASEsecurity-flow-deterministic-gates.md+ run approved deterministic gates and return unchanged findings withHIGH+|CLEAN|ERROR. - Expect: unchanged source records, evidence metadata,
HIGH+|CLEAN|ERROR. - Control: HIGH+ → report-and-package only; CLEAN → model-and-select; ERROR → stop. </deterministic_gates>
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 · 153 lines · 17 tokens per session scan A bb334e6edf24
security-flow is a command published in the GitHub repository griddynamics/rosetta (342 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 2,418 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
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.
/opsx-propose
Propose a new change - create it and generate all artifacts in one step.
/opsx-sync
Sync delta specs from a change to main specs.