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/far-200/think-before-code/debug-coachnpx skills add Far-200/think-before-code --skill debug-coachgit clone --depth 1 https://github.com/Far-200/think-before-codeWhat 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.00080 | $0.02702 |
| Opus 5 | $0.00040 | $0.01351 |
| Sonnet 5 | $0.00016 | $0.00540 |
| Haiku 4.5 | $0.00008 | $0.00270 |
Grade A, and why
debug-coach 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Coach
Why this exists
dsa-tutor lists "debug without replacing the learner's code" as one
stage among many in a full session. This skill is the deeper version
of that single stage, the same way complexity-coach is the deeper
version of dsa-tutor's verification question and dry-run-coach is
the deeper version of its dry-run stage.
Left alone, an LLM asked to debug code drifts toward the fastest fix: read the function, spot the issue, rewrite it, done. That produces correct code and teaches nothing. This skill exists to interrupt that drift and make the learner find the bug themselves.
Boundary with neighboring skills
-
vs.
dsa-tutor— dsa-tutor is for a learner who hasn't picked an approach yet, or is still constructing one. If no approach or code exists, this isn't the right skill; hand off to dsa-tutor. -
vs.
dry-run-coach— dry-run-coach traces an approach to build or verify a mental model, with or without a concrete failure yet. This skill starts from the opposite end: a specific piece of code and a specific observed failure that need to be traced back to a single divergence. If the learner has code and a bug, but hasn't actually run it against anything yet, send them throughdry-run-coach's tracing discipline first — there may be nothing to debug until a real input produces a real wrong output. -
vs.
specification-coach— this skill requires a stated expectation to diverge from. If the learner and their team haven't agreed what the code is supposed to do, there is no expected-vs-actual mismatch yet, only an undefined requirement; that'sspecification-coach.
Activation
Use this skill when the learner:
- has code or pseudocode they wrote themselves,
- can state what it's supposed to do,
- has observed it doing something else (wrong output, a crash, an infinite loop, a wrong edge case),
- and wants the bug found — not the function replaced.
Non-activation
Do not use this skill when:
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 · 284 lines · 80 tokens per session scan A c8f93b85a6fc
debug-coach is a skill published in the GitHub repository Far-200/think-before-code (8 stars, last pushed 17d ago), licensed MIT. It adds 80 tokens to every session and 2,702 once invoked, about $0.0004 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-31.
Other skills, from other repositories
interactive-leetcode-mcp
Use when the user wants to practice LeetCode problems, submit solutions, or set up LeetCode integration. Covers MCP server installation, learning-guided practice flow, solution submission, and authentication.
leetcode-helper
Expert LeetCode problem solver for optimized C++ coding interview solutions. Use when: the user pastes a LeetCode problem, asks for an optimized algorithm, wants C++ LeetCode code, needs a dry run, asks for line-by-line explanation, wants a hint before the solution, wants brute force to optimized progression, wants…
configure-profile
Create or update the global learner profile. Interviews the learner using the measurement checklist in references/PROFILE-TEMPLATE.md and writes the structured result to profile/PROFILE.md. Use when a new learner sets up Upstack for the first time, or after completing a course to update skills and Dreyfus levels.
complete-assignment
Run the reasoning review gate for a completed assignment. Asks 2-3 Reasoning Review Prompts from COURSE.md, verifies genuine understanding, and only marks the assignment complete if the learner demonstrates conceptual grasp. Use when a learner finishes an assignment and is ready for verification.
create-course
Scaffold a new course directory from the COURSE.md schema. Creates the directory structure, populates COURSE.md with YAML frontmatter and markdown template sections, and creates stub assignment directories. Use for curated courses (core/courses/) or personal courses (custom/courses/) in any domain.
start-course
Initialise a learning session. Checks for an existing journal in progress/ /journal.md, creates one from the template if missing, loads the course definition, and calibrates to the learner's declared context. Use when starting a new course or resuming after a break.