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 skills add griddynamics/rosetta --skill specflow-usegit 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/skills/griddynamics/rosetta/specflow-use)<a href="https://agentmods.dev/skills/griddynamics/rosetta/specflow-use"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/specflow-use/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/skills/griddynamics/rosetta/specflow-use"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/specflow-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00698 |
| Opus 5.5 | $0.00011 | $0.00279 |
| Sonnet 5.5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
specflow-use 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecFlow Use
This skill helps you drive Grid Dynamics SpecFlow from a local workspace via SpecFlow MCP. Rosetta stays local; SpecFlow runs everything remotely. The skill loads project context from gain.json and guides the user through SpecFlow MCP tool usage.
SpecFlow MCP is the only user interface to SpecFlow: you order work and download outputs. You do not connect to or operate on the remote workspaces directly.
Quick Start
When the user mentions SpecFlow or works in a SpecFlow-enabled project:
- Detect
gain.jsonat the workspace root (and up to 2 parents). If missing, SpecFlow MCP will create it on the first tool call (together withspecflow_session.json). - Load and summarize the project context.
- Guide the user to the right phase using
references/specflow-mcp-tools.md.
Step 1: Detect gain.json
Check for gain.json at the current workspace root. If not found, check parent directories up to 2 levels. If still missing, tell the user this workspace is not yet initialized for SpecFlow — the first SpecFlow MCP tool call will create both gain.json and specflow_session.json.
Step 2: Parse and Display Context
When gain.json is found, present a compact summary:
## SpecFlow Project Context
**Description**: [gain.json.description]
**Services**: specflow — [gain.json.servicesDescription.specflow]
rosetta — [gain.json.servicesDescription.rosetta]
**Supported Coding Agents**: [gain.json.codingAgents]
**Versions**:
- rosetta: [gain.json.versions.rosetta]
- specflow: [gain.json.versions.specflow]
**Vocabulary overrides** (if present in gain.json.vocabulary):
- (See references/specflow-vocabulary.md for defaults.)
Version Compatibility Check
Compare gain.json.versions.rosetta with the current Rosetta version:
- Minor difference: warn and continue.
- Major difference: alert the user about potential incompatibilities.
Step 3: Guide the User Journey
Read references/specflow-mcp-tools.md to route the user to the correct phase (pregeneration, generation, or post-run).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 72 lines · 27 tokens per session scan A 5e3bb6251249
specflow-use is a skill published in the GitHub repository griddynamics/rosetta (362 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 698 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.