Stripe Projects
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
Cost discipline for recurring /loop runs. An agent skill from Green-PT/honey-for-devs.
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Green-PT/honey-for-devs honey-loop --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/honey-loop .claude/skills/honey-loop && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .claude/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loopType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Green-PT/honey-for-devs honey-loop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/honey-loop .agents/skills/honey-loop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .agents/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Green-PT/honey-for-devs honey-loop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/honey-loop .cursor/skills/honey-loop && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .cursor/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Green-PT/honey-for-devs.git --path skills/honey-loop--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Green-PT/honey-for-devs honey-loop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/honey-loop .gemini/skills/honey-loop && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .gemini/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Green-PT/honey-for-devs honey-loopInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/honey-loop .github/skills/honey-loop && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .github/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Green-PT/honey-for-devs --skill honey-loop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Green-PT/honey-for-devs honey-loop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/honey-loop .opencode/skills/honey-loop && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "honey-loop" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-loop into .opencode/skills/honey-loop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-loop", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
honey-loopCost discipline for recurring /loop runs. An agent skill from Green-PT/honey-for-devs.
Honey Loop is an agent skill from Green-PT/honey-for-devs. Cost discipline for recurring /loop runs. A loop multiplies per-iteration cost by iteration count, so waste compounds. Encodes cache-aware pacing (avoid the 300s dead zone), event-driven-over-polling, a no-change short-circuit, a compact state handle carried between ticks, and a stop condition. Use when a /loop is running or being set up — especially long-lived or frequently-firing ones.
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Event-driven systems. The repository describes itself as: Honey (I Shrunk the AI) by GreenPT: a cross-tool coding skill that cuts AI coding-agent token usage and LLM API costs — write less code, less prose, and denser agent-to-agent… The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9169fc5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Honey Loop loads about 799 tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 427 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Green-PT/honey-for-devs at commit 9169fc5, republished under its MIT licence (© Green-PT). 427 words, ~799 tokens.
.claude/skills/honey-loop/SKILL.md (or your agent's skills folder).A loop is the one place token waste compounds: cost = per_tick × ticks. The
honey levers still apply inside each tick (less code, less prose), but a loop adds
two leaks the single-shot levers don't cover — re-paying for context every
wake-up, and re-doing work that didn't change. Cut those.
Pace to the cache, skip the dead zone. The prompt cache TTL is 5 min.
< 270s → context stays warm; right for actively polling external state.≥ 1200s → one cache miss amortized over a long idle wait; the default for
idle ticks (use 1200–1800s).~300s is the worst choice — pays the cache miss without amortizing it.
Never round to "5 minutes." Drop to 270s or commit to 1200s+.Event-driven over polling. Harness-tracked work (background Bash, Agent,
Workflow) re-invokes you automatically on completion. Don't schedule a short
tick to poll it — that re-reads full context for nothing. Set a long fallback
heartbeat (1200s+) and let the completion notification drive you. Poll only
external state the harness can't see (CI, a deploy, a remote queue), at a
cadence matched to how fast that state actually changes.
No-change short-circuit. Re-generating output is the bulk of per-tick cost.
Check cheaply first (a hash, a timestamp, a git rev-parse, a status field). If
nothing changed: emit one line and reschedule. Don't redo the task, don't
re-read the world, don't write a report.
Carry a compact state handle, don't re-derive. Keep what the loop has done
so far in a small file (.honey-loop/state.json or a <<honey:HASH>> stash via
eso stash), and read that each tick — not the full history re-discovered from
scratch. Lever 3b: the cheapest input token is the one that never re-enters context.
Define done; then stop. An unbounded loop is unbounded cost. State the exit condition up front (target reached, N empty ticks, deadline). When met, end the loop — omit the wake-up reschedule. "Loop forever" is a bug, not a feature.
A loop tick is an agent-to-self / agent-to-log message, not a deliverable. Default
to ultra: status line only, near-zero prose. One line is enough —
tick 4/∞ · no change · next 1800s. Step up to a full report only on the tick
where something actually needs the user (state changed, a decision, an error).
© Green-PT, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/honey-loop of Green-PT/honey-for-devs.
Open the folder on GitHubat commit 9169fc5
Honey Loop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Honey Loop this skillGreen-PT/honey-for-devs | 313 | — | ~799 | Automated safety check: Pass | MIT | |
| Stripe Projectsfossasia/eventyay | 1.7k | 5 repos | ~2k | Automated safety check: Notes | Apache-2.0 | |
| MQTTX CLIemqx/MQTTX | 5.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Windmill Trigger Type Checklistwindmill-labs/windmill | 18k | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 |
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
emqx/MQTTX
Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
xiaotianfotos/homerail
Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.
Green-PT/honey-for-devs
Write less code and say less about it. An agent skill from Green-PT/honey-for-devs.
Green-PT/honey-for-devs
Compress-Cache-Retrieve for huge, repetitive array tool output (logs, scan results, time series, event streams) before it enters context.
Green-PT/honey-for-devs
Report this session's output tokens and CO₂ by running the repo's committed EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always labelled with the bench stamp it came from.
Green-PT/honey-for-devs
Show Honey's benchmark scoreboard — the committed quality and token results per task tier (code, user-facing, agent-to-agent) from bench/.
Green-PT/honey-for-devs
Read huge, dense, read-only text as rendered PNG pages instead of raw text — image tokens scale with pixels, not characters, so token-dense bulk (big files, vendored code, diffs, logs) costs ~60–75%…
Green-PT/honey-for-devs
Stack Honey onto Superpowers-style workflows (subagent-driven-development, dispatching-parallel-agents, executing-plans) and any orchestration that dispatches fresh subagents.
Categories
Cost discipline for recurring /loop runs. An agent skill from Green-PT/honey-for-devs. Honey Loop is an agent skill from Green-PT/honey-for-devs. Cost discipline for recurring /loop runs.
Honey Loop fits situations like: A /loop is running; being set up — especially long-lived; frequently-firing ones.
Run `npx skills add Green-PT/honey-for-devs --skill honey-loop -a claude-code`. Or copy the skill folder (skills/honey-loop in Green-PT/honey-for-devs) into .claude/skills/honey-loop in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Green-PT/honey-for-devs --skill honey-loop -a codex`. Or copy the skill folder (skills/honey-loop in Green-PT/honey-for-devs) into .agents/skills/honey-loop in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Green-PT/honey-for-devs --skill honey-loop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/honey-loop, .gemini/skills/honey-loop, .github/skills/honey-loop and .opencode/skills/honey-loop in your project.
Going by SKILL.md and its folder, Honey Loop needs the command-line tools its instructions call (git).
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Honey Loop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 799 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Honey Loop: Stripe Projects (fossasia/eventyay, 1.7k stars), MQTTX CLI (emqx/MQTTX, 5.1k stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Green-PT (a GitHub organization) maintains it in Green-PT/honey-for-devs, which has 313 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 7, 2026.
Source: Green-PT/honey-for-devs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.