Pipelines

Pick a pipeline. See what it saves.

Reviewed add-ons for rtk, listed with what they save and what they need. How listing works

All reviewed pipelines

  • laya-tiered

    aeppling Cuts cost

    Sends file reads and shell commands to a worker model, compresses shell commands output, and briefs your agent.

    Result Total cost −20.2% per trial Author's benchmark
    Quality About the same
    Needs
    • Laya (local)
    • Anthropic key
    Stars 0

  • laya-delegate

    aeppling Cuts cost

    Sends file reads and shell commands to a worker model, and briefs your agent.

    Result Total cost −13.9% per trial Author's benchmark
    Quality Unchanged
    Needs
    • Laya (local)
    • Anthropic key
    Stars 4

  • default-bash-compress

    aeppling Cuts cost

    Turns on RTK's default pipeline with 1 built-in rule changed. Adds nothing else.

    Result Total cost −6.2% per trial Author's benchmark
    Quality About the same
    Needs
    • Nothing extra
    Stars 0

No pipelines match. Clear the filters.

View all community pipelines on GitHub Not reviewed by RTK. Read a pipeline's file before you install it.

How a pipeline gets here, and how to publish yours

Results are labelled by evidence. Measured by RTK: our CI. Author's benchmark: an A/B run the author published. Author's own usage: what their rtk counted on their traffic. Only a benchmark measures total cost; usage numbers measure output size, how much smaller tool outputs got.

  1. Run rtk pipeline share publish and choose GitHub repository. rtk creates the public repo in your account with your pipeline.toml, the rtk-pipeline topic and a README card carrying your own usage numbers. That is all it takes.
  2. Optional: to show a benchmark, add a benchmark.toml to that repo with the cost per trial with and without your pipeline, an optional quality metric, per task. Format.
  3. Within six hours a bot pre-checks the new commit with the standard rtk binary and opens a review in rtk-ai/pipelines.
  4. An RTK maintainer reads it and merges. Only merged versions appear here, pinned to that commit.
  5. Stars on your repo are the votes. Forks are remixes. Each pipeline has a discussion thread and a report link.

Machine-readable: index.json · RSS