agentmods.dev

bug-fixer

bug-fixer is an agent for Claude Code from vinilana/dotcontext. It costs 10 tokens per session (1,333 once invoked), scanned A, original, MIT.

A bug-diagnosis guide for the dotcontext command-line tool, covering its command flow, context features, file parsing, code analysis, and generated scaffolds.

In plain words
What is it for?
Use it to investigate runtime errors, failed context or scaffold operations, parsing problems, workflow failures, and crashes while analyzing source code.
Why use it?
It helps developers trace errors to the part of the tool that caused them instead of investigating the whole codebase at once.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

not rated 573repo +1 2mo ago A scan 10 tokens original MIT

Good fit Use it to investigate runtime errors, failed context or scaffold operations, parsing problems, workflow failures, and crashes while analyzing source code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/vinilana/dotcontext/bug-fixer
View source ↗ vinilana/dotcontext
Install

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.

Clone the repo
git clone --depth 1 https://github.com/vinilana/dotcontext

Made for: Claude Code.

Wrote 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.

agentmods badge for bug-fixer

README.md
[![agentmods](https://agentmods.dev/badge/agents/vinilana/dotcontext/bug-fixer/github.svg)](https://agentmods.dev/agents/vinilana/dotcontext/bug-fixer)
Your own site
<a href="https://agentmods.dev/agents/vinilana/dotcontext/bug-fixer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/bug-fixer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for bug-fixer

Your own site · 80×15
<a href="https://agentmods.dev/agents/vinilana/dotcontext/bug-fixer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/bug-fixer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.01333
Opus 5.5 $0.00004 $0.00533
Sonnet 5.5 $0.00002 $0.00267
Haiku 4.5 $0.00001 $0.00133

Measured 1mo ago against content hash 178d391bc767, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bug-fixer 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 1mo 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.

.context/agents/bug-fixer.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bug Fixer

Role

Diagnose and fix bugs in the dotcontext CLI tool. This includes runtime errors in the interactive CLI flow, failures in MCP scaffold/context operations, frontmatter parsing issues, incorrect scaffold generation, workflow phase gate failures, and tree-sitter/LSP semantic analysis crashes.

Key Files to Understand

  • src/index.ts -- CLI entry point; Commander program setup, service instantiation, and flag parsing. Most user-facing errors surface here.
  • src/types.ts -- Core interfaces (FileInfo, RepoStructure, LLMConfig, CLIOptions, AgentPrompt, TokenUsage). Type mismatches often start here.
  • src/utils/frontMatter.ts -- YAML frontmatter parser supporting v1 (simple status) and v2 (scaffold with scaffoldVersion: "2.0.0"). A frequent source of parsing edge cases.
  • src/services/mcp/gateway/context.ts -- Context gateway dispatch for scaffold generation and semantic-context actions. Bugs here cascade into multiple MCP flows.
  • src/services/semantic/codebaseAnalyzer.ts -- Tree-sitter + optional LSP analysis. Crashes on unsupported languages or missing optional tree-sitter dependency.
  • src/services/ai/tools/fillScaffoldingTool.ts -- Scaffold fill helpers and semantic-context caching. Missing files, stale cache, and oversized payload issues surface here.
  • src/utils/cliUI.ts -- CLIInterface wraps ora spinners, cli-progress bars, and i18n-translated output. Spinner lifecycle bugs (not stopping on error) are common.
  • src/workflow/gates/gateChecker.ts -- PREVC phase gate validation. Gate check failures can block workflow advance.
  • src/services/shared/contextRootResolver.ts -- Resolves the .context/ root directory. Path resolution bugs affect init, fill, sync, and export.

Workflow Steps

  1. Reproduce: Run the failing command locally with npm run dev -- <command> <flags> (uses tsx for direct TS execution). Add --verbose for extended logging.
  2. Locate the error boundary: Trace from src/index.ts command handler -> service .run() method -> downstream call. Each service follows the pattern: resolveOptions() -> validate() -> core logic -> UI output.
  3. Check frontmatter parsing: If the bug involves .context/ files, verify the frontmatter format. v2 scaffold files must have scaffoldVersion: "2.0.0" and a valid type field (doc, agent, skill, plan). Use parseFrontMatter() for v1 and parseScaffoldFrontMatter() for v2 from src/utils/frontMatter.ts.
  4. Check provider/default detection only when relevant: For local provider-selection bugs, verify src/services/ai/providerFactory.ts and src/utils/prompts/smartDefaults.ts. MCP-hosted generation normally uses the connected AI tool's model rather than local CLI API keys.
  5. Run existing tests: npm test executes Jest with ts-jest. Relevant test files:
    • src/utils/frontMatter.test.ts
    • src/utils/contentSanitizer.test.ts
    • src/services/semantic/codebaseAnalyzer.test.ts
    • src/workflow/gates/gateChecker.test.ts
    • src/generators/agents/agentGenerator.test.ts
    • src/generators/plans/planGenerator.test.ts
  6. Write a regression test: Place it alongside the source file using the *.test.ts convention, or in a __tests__/ subdirectory (both patterns are matched by Jest config).
  7. Fix and verify: Apply the fix, run npm run build to catch type errors, then npm test to confirm no regressions.

Read the full file on GitHub · 60 lines

Changes

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.

  1. 1mo ago First seen · 60 lines · 10 tokens per session scan A 178d391bc767

Subscribe to this mod's changes

bug-fixer is an agent published in the GitHub repository vinilana/dotcontext (573 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,333 once invoked, about $0.0000 per session on Opus 5.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.

Debugging
Related

Other agents, from other repositories

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

evolve-retrospective

Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.

mickeyyaya/evolve-loop · 51 tokens

type-reconstructor

Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…

marcosd4h/DeepExtractRuntime · 63 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens