Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/gcwing/bitfun/gstack-plan-eng-reviewnpx skills add GCWing/BitFun --skill gstack-plan-eng-reviewgit clone --depth 1 https://github.com/GCWing/BitFunWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gcwing/bitfun/gstack-plan-eng-review)<a href="https://agentmods.dev/skills/gcwing/bitfun/gstack-plan-eng-review"><img src="https://agentmods.dev/badge/skills/gcwing/bitfun/gstack-plan-eng-review.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00116 | $0.12353 |
| Opus 5 | $0.00058 | $0.06177 |
| Sonnet 5 | $0.00023 | $0.02471 |
| Haiku 4.5 | $0.00012 | $0.01235 |
Grade A, and why
plan-eng-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-eng-review — 86% identical, 629 lines differ
How it starts
The opening of the file, as written. The whole thing — 860 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Review Mode
Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
BitFun Team Mode Dispatch
When this skill is invoked by BitFun Team Mode, this skill supplies the engineering-manager review lens. Use existing Task sub-agents for independent architecture and evidence gathering, then synthesize decisions in the main Team session.
- Do not assume an Eng Manager sub-agent exists. Choose only from the Task tool's available agents.
- Prefer a matching custom architecture/backend/frontend/test sub-agent if available; otherwise use
Explorefor architecture mapping andFileFinderfor locating touched modules, plans, configs, and tests. - Keep Task work read-only before Build. Ask for data flows, edge cases, platform-boundary risks, test gaps, migration risks, and verification commands.
- In parallel plan-review batches, return a compact Eng brief:
architecture blockers,edge cases,test matrix,files likely touched,recommended implementation sequence. - The main Team orchestrator owns final plan edits, user questions, and build approval.
Priority hierarchy
If the user asks you to compress or the system triggers context compaction: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. Do not preemptively warn about context limits -- the system handles compaction automatically.
My engineering preferences (use these to guide your recommendations):
- DRY is important—flag repetition aggressively.
- Well-tested code is non-negotiable; I'd rather have too many tests than too few.
- I want code that's "engineered enough" — not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity).
- I err on the side of handling more edge cases, not fewer; thoughtfulness > speed.
- Bias toward explicit over clever.
- Minimal diff: achieve the goal with the fewest new abstractions and files touched.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 860 lines · 116 tokens per session scan A fc084f7efd91
plan-eng-review is a skill published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 12,353 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-delegation
将所有 git 操作委托给 Manager 执行。Worker 无法直接访问 git credentials，因此任何需要认证的 git 操作（clone、push、fetch 等）都需要通过此机制委托给 Manager。.
agentteams-migrate
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker.
workerflow-internal-workflow
Use when a QwenPaw-backed Worker needs to decide whether to do work directly, use native subagents for internal parallelism, or create a temporary QwenPaw agent with a custom AGENTS.md and skills.
find-skills
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
higress-gateway-management
Manage the Higress AI Gateway via its Console API (consumers, routes, AI providers, MCP servers). Use when creating consumers, configuring routes, or managing AI gateway settings.
worker-management
Use when admin requests hand-creating or resetting a Worker, starting/stopping a Worker, managing Worker skills, enabling peer mentions, or opening a QwenPaw console. Use agentteams-find-worker only as a helper for Nacos-backed market import or when task assignment needs you to discover a suitable Worker.