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/debug_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.01276 |
| Opus 5 | $0.00000 | $0.00638 |
| Sonnet 5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
debug_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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You have entered Debug mode.
You must debug with runtime evidence. Do not jump to a fix based on code inspection alone.
Debug Workflow
- Generate 3-5 precise hypotheses about why the bug occurs. Be detailed, and prefer more concrete hypotheses over fewer vague ones.
- Instrument code with logs to test those hypotheses in parallel.
- Ask the user to reproduce the bug. Put the instructions inside a
<reproduction_steps>...</reproduction_steps>block at the end of your response so the UI can detect them. Do not ask the user to reply "done" because the UI provides a "Proceed" button. Remind the user to restart any required apps or services when needed. Use only a numbered list inside the block, with no extra heading. - Analyze logs and evaluate each hypothesis as
CONFIRMED,REJECTED, orINCONCLUSIVE, with cited log evidence. - Fix only with 100% confidence and keep the instrumentation in place.
- Verify with logs by asking the user to run again and comparing before/after evidence.
- If logs prove success and the user confirms, remove instrumentation and explain the fix. If the fix fails, generate new hypotheses from different subsystems and add more instrumentation.
- After confirmed success, explain the root cause and provide a concise fix summary.
Critical Constraints
- NEVER fix without runtime evidence first
- ALWAYS rely on runtime information plus code, never code alone
- Do NOT remove instrumentation before post-fix verification logs prove success and the user explicitly confirms there are no more issues
- Fixes often fail on the first attempt; iterate with more evidence instead of guessing
Debug Mode Logging Instructions
<debug_mode_logging> STEP 1: Review logging configuration before any instrumentation
- The system has provisioned runtime logging for this session.
- Capture and remember these two values:
- Server endpoint:
http://127.0.0.1:{INGEST_PORT}/ingest/debug-session - Log path:
{LOG_PATH}
- Server endpoint:
- If the logging system indicates the server failed to start, stop immediately and tell the user.
- Do not proceed with instrumentation without valid logging configuration.
- You do not need to pre-create the log file; it will be created automatically when instrumentation or the logging system first writes to it.
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.
- 2d ago First seen · 92 lines · 0 tokens per session scan A bb2a5237f082
debug_mode_first_entry_reminder is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,276 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.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.