A zero-dependency logging proxy that sits between Claude Code and the Anthropic API. It forwards every request untouched, streams the reply straight back (so the CLI is unaffected), and writes a readable Markdown document for each request — led by a ranked table of what is eating your context.
| /** | |
| * HttpBaseClient — a self-contained, framework-agnostic abstract HTTP client. | |
| * | |
| * Design goals: | |
| * - Single file, zero dependencies (Node 18+ / browser). | |
| * - Every outbound HTTP call goes through one pipeline so you get | |
| * consistent logging, error mapping, metrics, and query/body | |
| * serialization for free. | |
| * - Subclasses focus on vendor specifics: base URL, auth headers, | |
| * and optional error-body translation. |
| name | cook |
|---|---|
| description | Code in an Opus session, using Fable subagent to plan and Codex to write code and finally Fable subagent review for every task. |
| user-invokable | true |
Implement all tasks given to you. Use a Fable high subagent to write a plan.md for each task. Require my approval for all plans before beginning implementation. Then write all code by calling out to codex exec for each task using codex --yolo exec -c model="gpt-5.5" -c model_reasoning_effort="high" < plan.md (allow cmd to run for up to 20 minutes), then review code (using a subagent with Fable high) and smoke testing new features (usage a subagent with Opus medium) by running pnpm dev and doing real requests, before committing and pushing, then moving onto next task. Remember that every subagent or codex session is completely independent and must be given the full context it needs to complete its work.
Securely connect to Android over the internet using ADB + Tailscale.
You can also copy paste this gist into your agent of choice and have it explain you what to do.
This guide sets up remote ADB access so you can run android-use — an agent skill that lets AI interact with your Android device over ADB.
| Tool / Project | Type / Architecture | UI / Dashboard | CLI / API | Multi‑node / Clustering | Auto TLS / SSL / ACME | Zero‑downtime / Rolling Deploy | Preview / PR Environments | Team / Permissions | Volume / Backup Support | Open Source / License | Heroku‑style Compatibility | Pros / Strengths | Cons / Caveats / Weaknesses |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dokku | Single‑server (extensions for multi) | Minimal (no central UI, though plugins exist) | CLI, plugin APIs | Via community / plugin / custom setups | Yes (Let’s Encrypt plugin) | Via Docker techniques / plugin | Limited, requires extra setup | Basic (single admin; community plugins) | Plugin / manual (e.g. volume backups) | MIT (fully open source) | Good: git push, buildpack style, plugins add DB, etc. | Very stable, mature, lots of community extensions | Scaling / multi‑node is manual; UI is weak; managing many apps / teams is harder |
| Dokploy | Multi‑node / cluster (Docker Swarm) | Yes (built‑in UI) | CLI + AP |
| { | |
| "hooks": { | |
| "PostToolUse": [ | |
| { | |
| "matcher": "Write|Edit", | |
| "hooks": [ | |
| { | |
| "type": "command", | |
| "command": "~/scripts/doc-generator.sh" | |
| } |
This guide outlines the steps to set up an SSH server and Tailscale on a fresh Debian installation inside the Android Linux Terminal App. After completing these steps, you'll be able to securely SSH into the Linux environment running on your Android device from any remote machine over the internet using Tailscale.
-
Update package lists and upgrade installed packages to the latest versions:
sudo apt update && sudo apt upgrade -y
If you are a React Native, NativeScript, Flutter or Ionic developer maybe you don't want to install the entire Android Studio just to have your environment ready. If this is your case, this guide will help you to setup your minimal Android SDK environment in Windows.

