DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add the Grok Build project surface to a repo with Ruflo

Write Ruflo's Grok host files into one project, previewing first with a dry run.

Authorization notice. Ruflo is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer using Grok Build who wants Ruflo's project files and team bus inside a single repository.

The problemSetting up a new agent host by hand means writing host files and checking their contents without a preview.

The outcomeA .grok/ folder, team bus and operator guide are written into the project, with nothing outside it.

What you need first

  • Node.js with npx available in your project terminal
  • Claude Code 2.1.287 or later for the Claude Code plugin path
  • An MCP-enabled client such as Codex if you use the MCP path
  • Review the code of any mod before installing it, since mods run with your account's permissions

Steps

  1. Run npx ruflo init --grok --dry-run in the project to preview the files. (inferred, check the README)
  2. Run npx ruflo init --grok to write the project host surface.
  3. Read the Grok operator guide at v3/@claude-flow/cli/templates/grok/docs/README.md before using the spawn_subagent contract.
  4. Re-check the setup when Grok updates, as the README advises.

Prompt for your agent

Using the repo ruvnet/ruflo, preview then write the Grok Build project surface into <project path> with `npx ruflo init --grok`. Expected output: a .grok/ folder and team bus files inside the project only. Verify that no files were written outside the project directory.

Caveat. The README says the Grok setup should be re-checked when Grok updates, so the surface may need changes after an update.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page