←
StarSling (YC X25)142 posts
StarSling (YC X25) avatar

StarSling (YC X25)

@starslingdev

Agent-native CI. Trusted by @mastra, @better_auth, and other AI-first companies. Backed by @ycombinator. Free skills: github.com/starslingdev/skil…

◷ Joined April 2025▧ 5 Photos and videos
Micky avatar
⟳ StarSling (YC X25) retweeted
Micky@Rasmic·14h

Don’t sleep at on @yonasbe this man will single handily lower your CI bill

It’s time to put a stop to runaway CI bills. Introducing the CI Challenge 🤑 If @starslingdev can’t save you 10% or more on your CI bill, we’ll pay you $1,000. We’ve done over 5M CI jobs in production and have shipped hundreds of CI fixes to customer's repos, saving them over 50,000 hours in compute. Today we released new benchmarks: in 9 popular open source repos, we got an average 10x speedup in wall clock time with 70% less runner time (benchmarks linked in the post). How the challenge works: - Confirm you’re eligible + signup - Start using StarSling Runners - Start saving right away with faster runners + per second billing - Once you hit 10,000 minutes StarSling agents start sending you PRs to chop down your bill We want to help more companies remove the CI bottleneck and reduce their bill with faster runners and agents that cut down your minutes. There’s literally no reason not to do this if you’re trying to get your CI costs down. You keep whatever improvements our agents ship to you, and if we can't cut down your bill by 10% or more, you make money! How to enter the challenge:

0:19
Daniel Worku avatar
⟳ StarSling (YC X25) retweeted
Daniel Worku@dbworku·20h

Cheaper CI or you get paid.

It’s time to put a stop to runaway CI bills. Introducing the CI Challenge 🤑 If @starslingdev can’t save you 10% or more on your CI bill, we’ll pay you $1,000. We’ve done over 5M CI jobs in production and have shipped hundreds of CI fixes to customer's repos, saving them over 50,000 hours in compute. Today we released new benchmarks: in 9 popular open source repos, we got an average 10x speedup in wall clock time with 70% less runner time (benchmarks linked in the post). How the challenge works: - Confirm you’re eligible + signup - Start using StarSling Runners - Start saving right away with faster runners + per second billing - Once you hit 10,000 minutes StarSling agents start sending you PRs to chop down your bill We want to help more companies remove the CI bottleneck and reduce their bill with faster runners and agents that cut down your minutes. There’s literally no reason not to do this if you’re trying to get your CI costs down. You keep whatever improvements our agents ship to you, and if we can't cut down your bill by 10% or more, you make money! How to enter the challenge:

0:19
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·20h

It’s time to put a stop to runaway CI bills. Introducing the CI Challenge 🤑 If @starslingdev can’t save you 10% or more on your CI bill, we’ll pay you $1,000. We’ve done over 5M CI jobs in production and have shipped hundreds of CI fixes to customer's repos, saving them over 50,000 hours in compute. Today we released new benchmarks: in 9 popular open source repos, we got an average 10x speedup in wall clock time with 70% less runner time (benchmarks linked in the post). How the challenge works: - Confirm you’re eligible + signup - Start using StarSling Runners - Start saving right away with faster runners + per second billing - Once you hit 10,000 minutes StarSling agents start sending you PRs to chop down your bill We want to help more companies remove the CI bottleneck and reduce their bill with faster runners and agents that cut down your minutes. There’s literally no reason not to do this if you’re trying to get your CI costs down. You keep whatever improvements our agents ship to you, and if we can't cut down your bill by 10% or more, you make money! How to enter the challenge:

0:19
StarSling (YC X25) avatar
StarSling (YC X25)@starslingdev·20h

Who’s going to step up to the plate? 👀

It’s time to put a stop to runaway CI bills. Introducing the CI Challenge 🤑 If @starslingdev can’t save you 10% or more on your CI bill, we’ll pay you $1,000. We’ve done over 5M CI jobs in production and have shipped hundreds of CI fixes to customer's repos, saving them over 50,000 hours in compute. Today we released new benchmarks: in 9 popular open source repos, we got an average 10x speedup in wall clock time with 70% less runner time (benchmarks linked in the post). How the challenge works: - Confirm you’re eligible + signup - Start using StarSling Runners - Start saving right away with faster runners + per second billing - Once you hit 10,000 minutes StarSling agents start sending you PRs to chop down your bill We want to help more companies remove the CI bottleneck and reduce their bill with faster runners and agents that cut down your minutes. There’s literally no reason not to do this if you’re trying to get your CI costs down. You keep whatever improvements our agents ship to you, and if we can't cut down your bill by 10% or more, you make money! How to enter the challenge:

0:19
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 17

Love this! @DanielLockyer opened 9 PRs on open source repos to speed up and improve their CI and one of them cut a repo's CI time by 65%. The changes: 1. Run Playwright with more than one worker in CI 2. Run CI once per commit, and cancel runs a newer commit has replaced 3. Save the cache on main, so release tags can restore it 4. Run tests beside the builds instead of after them 5. Stop running the same test suite or build twice in one job 6. Build coverage libraries without debug info 7. Keep actions on their current versions ci-speedup checks your repo for all of these, using your own runs: npx skills add starslingdev/skills --skill ci-speedup

Post attachmentPost attachment

9 PRs opened on OSS projects to speed up/improve CI :)

Post attachment
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 15

Instructions to get your CI under 2 minutes 💫 Pontus' prompt is great. Here's an updated version that goes further (attached). Instead of the 18 fixes he called out, your agent runs the ci-speedup skill, which does an audit and checks it against 90+ patterns. Prompt attached also covers slowdowns that show up outside the frontend: Playwright installs, Turborepo cache misses, fixed sleeps in tests and unused service containers. And it swaps in @starslingdev runners which no support per second billing (that part isn't in the skill). Same two rules as @pontusab's: the full suite runs before main, and you never get faster by hiding failures. Give the image to your agent, or give them this URL: github.com/starslingdev/skil…

Post attachment

Instructions to get your CI under 2 minutes ⚡

Post attachment
Daniel Worku avatar
⟳ StarSling (YC X25) retweeted
Daniel Worku@dbworku·Nov 13

Introducing Disks... Persistent filesystems mounted to @starslingdev GitHub Actions jobs that are ready 10.5x faster than an actions/cache. Up to 2TB mounted per job. No practical limit to read concurrency, folder nesting depth or number of files.

0:20
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 13

11.6x faster 🔥 StarSling Disks vs GitHub actions/cache, same 4.5 GiB pnpm store (234,900 files): - GitHub: 34.7s until files are readable - StarSling Disks: 3.0s github.com/starslingdev/disk…

0:19

Introducing Disks... Persistent filesystems mounted to @starslingdev GitHub Actions jobs that are ready 10.5x faster than an actions/cache. Up to 2TB mounted per job. No practical limit to read concurrency, folder nesting depth or number of files.

0:20
StarSling (YC X25) avatar
StarSling (YC X25)@starslingdev·Nov 13

Introducing StarSling Disks 💾

Introducing Disks... Persistent filesystems mounted to @starslingdev GitHub Actions jobs that are ready 10.5x faster than an actions/cache. Up to 2TB mounted per job. No practical limit to read concurrency, folder nesting depth or number of files.

0:20
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 12

TL;DR of the GitHub Actions CI secret stealer campaign (and how to check your own repos for it) ⬇️ What happened: attackers used stolen GitHub tokens to push a payload into every repo those tokens could write to. Usually it was steps added to an existing workflow that handed the entire secrets context to a stealer script. Sometimes it was a package.json install hook or a new workflow on a throwaway branch. CI ran it with the repo's secrets and sent them out. Within a minute it was reverted and the run was deleted. No pull request was merged and nobody reviewed anything. What had to be true along the way: 1. A token was stolen from an account that could push to the repo, including workflow files. 2. A workflow on the branch they pushed to could read the repo's secrets. Repo and org secrets work that way by default. Secrets in an environment limited to protected branches don't. 3. For a push to the main branch, nothing required a reviewed pull request, or the account was allowed to skip that review. 4. Nobody noticed. Aikido says 92% of the probe pull requests are still open. Fix both 2 and 3 and a stolen non-admin token can't reach your secrets. A stolen admin token beats both, so 1 matters too. The payload used the same whole-secrets dump that ci-secure (@starslingdev skill) already flags in workflow files. But it was live for under a minute, so no file scan would ever see it. The defense has to be in your settings, so ci-secure now checks 2 and 3 too. Using your own gh login, read-only, it reads your settings and: - names any secrets a workflow on any branch can read (never their values), and says to move them into an environment only protected branches can use - fails your main branch if anyone short of an admin can get code in without a reviewed pull request, counting bypass apps, teams and "pull requests only" bypasses - reports a setting it can't read as unmeasured rather than passing it To try it, run: npx skills add starslingdev/skills --skill ci-secure Then ask your agent "is my CI secure?" It scans your repo and walks you through fixing anything it finds. Repo: github.com/starslingdev/skil…

🚨 Massive GitHub Actions CI Secret Stealer 4,800+ compromised accounts attempted to push malicious workflows to 61k+ repos. Payload dumps all CI secrets, memory, OIDC & commit secrets, then instantly deletes run logs. Search your repos for: • PR: "docs: dependency audit notes" • Branch: wfx-docs or chore/ • Commits: "ci: refresh build cache" or "chore: add ci helper" • Actions tab: Skipped/missing run numbers If hit, assume total compromise. Rotate ALL secrets and cloud roles immediately.

Post attachment
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 12

"Lock your GitHub Actions" is trending, and it's good advice. GitHub's new workflow lockfiles let you keep readable version tags in your workflows while every run still executes the exact commit you locked. ci-secure (@starslingdev skill), now understands lockfiles and tells you what they do and don't protect. How it works: it reads your actions.lock straight from the repo, offline, and tells you how many of your actions it covers. GitHub verifies those commits on every run, so a locked action can't be swapped out from under you. It counts only what the lockfile really protects. Reusable workflows called from other repos aren't locked, so they don't get credit, and a broken or malformed lockfile gets none either. It also covers a gap lockfiles can't: tools your jobs install with shell commands. If a job installs a gh CLI extension at a version that can still change and then runs it, every run executes whatever is published there at that moment, holding your job's token. ci-secure flags that, and the fix depends on how the extension ships: a commit pin for script extensions, an immutable release (or a verified download) for prebuilt ones. When the release is already immutable, it stays quiet. To try it, run: npx skills add starslingdev/skills --skill ci-secure Then ask your agent "is my CI secure?" It scans your workflows locally and walks you through fixing anything it finds. github.com/starslingdev/skil…

Post attachment
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 10

Thanks for the shout out @DanKornas! @starslingdev skills run against your own GitHub Actions setup: - 🏎️ ci-speedup finds where your workflows waste time - 📋 ci-score rates your CI setup - 🔒 ci-secure flags security risks in your workflows github.com/starslingdev/skil…

Slow GitHub Actions? Give your coding agent a CI audit kit. StarSling Skills is a collection of agent skills for builders optimizing GitHub Actions workflows. It helps you investigate slow runs, check workflow configuration, and spot specific security risks by combining local workflow audits with run-history analysis. Key features: • ci-speedup – uses run history to separate developer wait time from runner-minutes, so you can distinguish delays from compute usage • ci-score – checks 11 configuration practices, including caching, timeouts, and concurrency cancellation, with a ranked fix for each failed check • ci-secure – scans for ten attack vectors, with findings that name the file, line, and what an attacker could do • Agent choice – install selected skills for Claude Code, Codex, or Cursor with npx skills add starslingdev/skills • Reviewable audit fixes – choose which findings to address or save a Markdown report; changes stay in your working tree for review It’s open-source (MIT license). Link in the reply 👇

Post attachment
Dan Kornas avatar
⟳ StarSling (YC X25) retweeted
Dan Kornas@DanKornas·Nov 10

Slow GitHub Actions? Give your coding agent a CI audit kit. StarSling Skills is a collection of agent skills for builders optimizing GitHub Actions workflows. It helps you investigate slow runs, check workflow configuration, and spot specific security risks by combining local workflow audits with run-history analysis. Key features: • ci-speedup – uses run history to separate developer wait time from runner-minutes, so you can distinguish delays from compute usage • ci-score – checks 11 configuration practices, including caching, timeouts, and concurrency cancellation, with a ranked fix for each failed check • ci-secure – scans for ten attack vectors, with findings that name the file, line, and what an attacker could do • Agent choice – install selected skills for Claude Code, Codex, or Cursor with npx skills add starslingdev/skills • Reviewable audit fixes – choose which findings to address or save a Markdown report; changes stay in your working tree for review It’s open-source (MIT license). Link in the reply 👇

Post attachment
Yonas Beshawred avatar
⟳ StarSling (YC X25) retweeted
Yonas Beshawred@yonasbe·Nov 10

We analyzed @StripeDev's public CI work (37 techniques from 38 PRs and 6 blog posts) and pulled out the moves that made their GitHub Actions faster and cheaper. Some of the biggest wins weren't about tests: - In their iOS SDK, some jobs spent up to 30+ minutes just fetching git history. When a shallow checkout can't find the merge base, git can fall back to fetching every branch. They switched to fetching only the PR and main histories, a little deeper each time, until the merge base turned up. Main gets about 130 commits a month, so most PRs are done in one or two fetches. - They were also rebuilding the same main-branch baseline on every PR just to compare API surfaces. Caching it by revision, toolchain, and build recipe, along with building less, took that check from about 14 minutes to about 4. The pattern: a lot of CI time is work you already did, fetched or built again because the job didn't know it could reuse it. Full playbook: starsling.dev/ci-playbooks/s…

A new GitHub Actions runner launches every week now. But getting faster runners is just one part of what the best engineering teams do to speed up their CI. Introducing CI Playbooks ▶️ an agent-friendly library of 253 GitHub Actions optimizations from companies running software factories. We analyzed 416 pull requests and commits, and 182 blog posts, talks, and podcasts from ten companies: 1. Anthropic: CI job volume grew 25x in six months as Claude came to write 80% of its code 2. DoorDash: build and test cut from 22 minutes to 6 3. Linear: jobs 34% faster while test suites almost quadrupled 4. Mastra: 29m 56s to 5m 06s p95 on StarSling runners 5. OpenAI: about 30 CI PRs took median CI from about 10 minutes to 4.5 6. Ramp: its coding agent accounts for 74% of merged PRs 7. Shopify: an agent running experiments made the Polaris build 65% faster 8. Spotify: deployer image build went from 2h28m to about 17 minutes 9. Stripe: runs about 5% of its full Ruby test suite per build 10. Uber: CI resource usage down 53%, wait times down 37% Some of these companies aren't using GitHub Actions as their CI engine internally so we translated all the optimizations they've talked about or made publicly in their repos, into their GHA equivalents. Every technique comes with its original source and a prompt your coding agent can run on your repo. Add .md to any playbook URL for the markdown version, or just hand this URL to your agent: starsling.dev/ci-playbooks There's tons to dig into here, I'm going to highlight some of the findings I found most interesting 🧵

0:24
StarSling (YC X25) avatar
StarSling (YC X25)@starslingdev·Nov 9

Lots of updates for ci-speedup! 🚀 github.com/starslingdev/skil… starsling.dev/skills/ci-spee…

Huge update to ci-speedup (@starslingdev's open source skill): last week we merged 80 more PRs. ci-speedup now checks for 97 ways GitHub Actions can waste time (prompt to install below). New checks: 1. Your Docker build compiles ARM code on an x64 runner through emulation, which can be several times slower than a native build. ci-speedup checks whether that step really dominates, then sizes two fixes: cross-compiling, or moving that build to a native ARM runner. 2. Your cache never actually warms up (from @HiTw93's prompt). It saves the wrong directory, the restore key can never match, or the cache gets wiped every run, so every run starts cold. 3. The same tests run twice: once for the required check and again for coverage, or in a second workflow on the same trigger (from @rchdlps's article). 4. Tests run one at a time when they could run in parallel (from @HiTw93's prompt): a shell loop that goes file by file, or tests that each wait on their own database. 5. Rust compiles the same crates twice in separate steps, and your test runner restarts a process for every file. ci-speedup reports are also more honest about where your time goes: - PR wait is measured per commit across every workflow, from the first run starting to the last job finishing, including time spent waiting for a runner. Queue time is broken down by runner label. - A separate section shows how long main takes after you merge. - After your agent pushes a fix, ci-speedup re-measures the next pushes against the old ones. It only claims a speedup when the runs are comparable: same work, same runners, same cache state. Install prompt: "Run `npx skills add starslingdev/skills --skill ci-speedup` to install or update the ci-speedup skill."