TGL — Touch Grass Later (Muse Agent Harness)
Turn a Muse coding agent into a disciplined build team — Plan Mode, then Attack Mode.
- What
- Turn a Muse coding agent into a disciplined build team — Plan Mode, then Attack Mode.
- Cost
- Free
- Needs
- A Muse coding agent to run the harness in (this installs into Muse itself). Python 3 on your machine only if you pick the TUI installer path (it's stdlib-only, works over plain SSH). No accounts, no API keys, no costs.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a free, open-source workflow (MIT) by Tom Nwachuku, listed here with credit to its creator. A spec-driven harness that turns a Muse coding agent into a disciplined build team: Plan Mode grills you one question at a time, writes a spec and a sliced plan, and waits for your sign-off before any code; Attack Mode then executes the plan slice by slice with reviews and red-teaming. Load its SKILL.md into your Muse agent and say "run TGL". Draft: Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Quick answer
TGL: Touch Grass Later is a free Muse skill that turns a Muse coding agent into a disciplined build team. Plan Mode asks one question at a time, writes a spec and a sliced plan, and waits for your sign-off before any code, then Attack Mode executes the plan slice by slice with reviews and red-teaming.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4d613c4Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: A Muse coding agent to run the harness in (this installs into Muse itself). Python 3 on your machine only if you pick the TUI installer path (it's stdlib-only, works over plain SSH). No accounts, no API keys, no costs. Install "TGL — Touch Grass Later (Muse Agent Harness)" for me. A free, open-source (MIT) developer harness by @tom-nwachuku that turns a Muse coding agent into a disciplined, spec-driven build team: Plan Mode grills you one question at a time, writes SPEC.md and a sliced PLAN.md, and waits for your sign-off before any code; Attack Mode then executes the plan slice by slice with reviews, SITREPs at every boundary, and a red-team pass before shipping. Repository: https://raw.githubusercontent.com/tom-nwachuku/tgl/4d613c46b284922b752a3f54f461194de14c93b7/SKILL.md Pinned version: install the code at commit 4d613c46b284922b752a3f54f461194de14c93b7 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone the repo into a temporary folder (public HTTPS clone — no account needed) and look inside. 2. Safety check: briefly review SKILL.md and install/tgl-install.py for anything suspicious (network calls to unexpected hosts, shell commands reaching beyond the install target, credential harvesting). The installer copies the skill into my Muse skills folder — that's by design. If you see a red flag, stop and tell me before going further. 3. Set up everything you can: install the skill following the repo's own flow — either the conversational path (read SKILL.md, walk me through setup step by step, explain both modes, offer the guided first-run tutorial from docs/tutorial.md; no terminal required) or the TUI installer (run python3 install/tgl-install.py; flags --yes, --no-color, --target DIR; press h at any prompt for help). Verify the install by reading the skill back from the install location, the way the repo's own installer does. Then give me the exact remaining manual steps (if any). 4. Verify with a safe dry run: confirm SKILL.md loads from my Muse skills folder and the SPEC/PLAN/LEDGER templates are present. Do not start a real Plan Mode or Attack Mode session without my explicit confirmation. 5. Report: what you installed, where, and anything still left for me to do myself (or confirm there's nothing left). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it (e.g. authenticated clone); otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me. Never start Attack Mode — which writes code — without my explicit sign-off on a plan first.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
What the scan found — excerpts from the install prompt
- runs commands — 3. Set up everything you can: install the skill following the repo's own flow — either the conversational path · 3. Configure tout ce que tu peux : installe le skill selon le parcours du repo — soit le parcours conversation
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4d613c4 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.