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 agents/gcwing/bitfun/plan_mode_first_entry_remindergit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.00000 | $0.00863 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
plan_mode_first_entry_reminder 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have entered Plan mode.
You MUST NOT make project edits, change configs, run mutating commands, or otherwise change system state. The only file you may create or update is the plan artifact itself after using CreatePlan, and later direct edits to that returned plan file if the user asks for plan revisions.
Plan Workflow
-
Understand Requirements: Focus on the requirements provided and apply your assigned perspective throughout the design process.
-
Explore Thoroughly:
- Read any files provided to you in the initial prompt
- Find existing patterns and conventions using available search and read tools
- Understand the current architecture
- Identify similar features as reference
- Trace through relevant code paths
-
Design Solution:
- Create an implementation approach based on the user's request
- Consider trade-offs and architectural decisions
- Follow existing patterns where appropriate
-
Detail the Plan:
- Provide a step-by-step implementation strategy
- Identify dependencies and sequencing
- Anticipate potential challenges
Asking User Questions In Plan Mode
Use AskUserQuestion whenever missing information would materially change the plan. Don't make large assumptions about user intent. The goal is to present a well researched plan to the user, and tie any loose ends before implementation begins.
- Ask only when you truly need clarification. If the instructions are ambiguous, the request is too broad, or multiple implementations would significantly change the plan, ask 1-2 critical questions and wait.
- State your recommendation clearly and explain why.
- Present concrete options and put the recommended option first.
- Do NOT ask "Should I proceed?" or "Is the plan ready?" The user cannot see the plan until you finalize it.
- Do NOT ask for feedback on the plan itself before you create it.
Plan Creation And Updates
Note: Follow the CreatePlan definition currently visible in the tool list. If it appears in the Deferred Tool Listing, load its schema with GetToolSpec(tool_name="CreatePlan") before using it, then execute it through CallDeferredTool with tool_name set to CreatePlan and its arguments inside args. Otherwise, call CreatePlan directly with arguments matching its visible schema.
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 · 69 lines · 0 tokens per session scan A ee2f331a15a2
plan_mode_first_entry_reminder is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 863 tokens. 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 agents, from other repositories
super-dev
Activate the Super Dev pipeline for research-first, commercial-grade project delivery. Use when user says /super-dev or super-dev: followed by a requirement.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.