stampede
Skill9 starsChanged 22 days agoMITView on GitHub
One ask starts a Herdr job run by a lead agent that opens panes only when it's worth it. Use when asked to use stampede, run a job with agents in Herdr, start a lead for an ask, or show the plan before a job starts.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- DUBSOpenHub/terminal-stampedetheir own version, first seen Apr 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- DUBSOpenHub/terminal-stampede★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- grokbot-herdrSkill
- herdr-fleetSkill
- share-planSkill
- stampedeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
The owner asks to see the plan first: read skills/share-plan/SKILL.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
stampede
The owner texts a task to a Grok Bot, which reaches the owner's Mac over Tailscale, and every update and question goes back through it (it works without a bot too). One ask, one lead, and a pane only when it's worth it. The lead plans in plan.md, works, and brings the owner only the questions and gates that are theirs.
- Starting a job (any chat the owner asks to use stampede): read skills/stampede/SKILL.md.
- Running the job (the lead, or a chat that will open panes): read skills/herdr-fleet/SKILL.md.
- A bot front door (outside Herdr, over SSH): read skills/grokbot-herdr/SKILL.md.
- The owner asks to see the plan first: read skills/share-plan/SKILL.md.
Front door
The front door is its own skill, installed as stampede: skills/stampede/SKILL.md. It sizes the job, writes the ask, opens a Herdr workspace for the project when the chat is outside Herdr, and starts the lead with stampede new (with --front-door when the chat is outside Herdr, and --fork when the plan was worked out in that chat). In a --front-door job it then relays the lead's outbox (plan, questions, gates, files) to the owner and their answers back. stampede is the same command as fleet-job.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.