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 skills/lukas-grigis/ralphctl/flow-trace-syncnpx skills add lukas-grigis/ralphctl --skill flow-trace-syncgit clone --depth 1 https://github.com/lukas-grigis/ralphctlWrote 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/lukas-grigis/ralphctl/flow-trace-sync)<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/flow-trace-sync"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/flow-trace-sync.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.00162 | $0.01169 |
| Opus 5 | $0.00081 | $0.00584 |
| Sonnet 5 | $0.00032 | $0.00234 |
| Haiku 4.5 | $0.00016 | $0.00117 |
Grade A, and why
flow-trace-sync 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Trace Sync
A ralphctl flow is a tree of named chain elements (sequential('implement', […]), guard('task-runnable-<id>', …), loop('task-attempts-<id>', …)). The order and names of those elements are the flow's observable shape —
and several docs describe it in prose or diagrams: the implementFlow example in KERNEL-DESIGN.md, the
sequence diagrams under .claude/docs/diagrams/, and the step-by-step criteria in REQUIREMENTS.md.
The code owns that shape in two places: the flow definition (the leaf/sequential/guard/loop('<name>')
calls) and the step-order fence test (which asserts trace.map(s => s.elementName) for happy + failure
paths — a test fails the moment the real order changes). The docs do not fail when they fall behind. So a
guard gets added, an element gets renamed, the loop nesting changes — the test is updated, the prose is not,
and the next reader trusts a sequence the harness no longer runs. This skill closes that gap.
When this earns its keep
- Right after you change a flow's element list — add/remove/reorder/rename a
leaf/sequential/guard/loop. - Before a release, alongside
drift-sweep, so the architecture docs ship accurate. - When a documented "A → B → C" trace looks wrong against the code.
How to run it
-
Extract the real element sequences:
bash .claude/skills/flow-trace-sync/scripts/flow-traces.sh # all flows bash .claude/skills/flow-trace-sync/scripts/flow-traces.sh implement # one flowFor each flow it lists the element names found in the definition (deduped, file order) and points at the fence test that asserts the canonical runtime sequence. Note: the listed order is definition order across files, not the exact runtime order — the fence test is authoritative for the precise sequence, so open it when order matters.
-
Locate the documented traces that describe the changed flow:
KERNEL-DESIGN.md— worked flow examples (e.g.implementFlow)..claude/docs/diagrams/— the sequence / lifecycle diagrams.REQUIREMENTS.md— criteria that spell out an attempt/loop body order.
What ships with it
1 file 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.
- 4d ago First seen · 67 lines · 162 tokens per session scan A a7e7bc8c8252
flow-trace-sync is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed today), licensed MIT. It adds 162 tokens to every session and 1,169 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-copilot-provider
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode.
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
macos-swiftpm
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
fix-codesign-error
Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.