agentmods.dev

SEPCC: Agent for Claude Code

.claude/agents/fcc-agent-debugger.md

fcc-agent-debugger is an agent for Claude Code from sepehrbayat/SEPCC. It costs 34 tokens per session (1,174 once invoked), scanned A, original, MIT.

A reviewer that examines work completed by another coding agent and produces a structured report of problems. It checks correctness, completeness, and whether the required process was followed.

In plain words
What is it for?
Use it to inspect the other agent’s task description, transcript, changed files, commits, and test results, then report specific issues with evidence.
Why use it?
It helps find bugs, missing work, and workflow violations before the changes are accepted.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; mentions subagents.

This is sepehrbayat/SEPCC's own configuration. It tells Claude Code how to work on SEPCC itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SEPCC configures →

not rated 43repo +1 2mo ago A scan 34 tokens original MIT
View source ↗ sepehrbayat/SEPCC
Reuse

Borrowing it

Nothing to install: this file belongs to sepehrbayat/SEPCC. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sepehrbayat/SEPCC/main/.claude/agents/fcc-agent-debugger.md
Clone the repo
git clone --depth 1 https://github.com/sepehrbayat/SEPCC

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 fcc-agent-debugger

README.md
[![agentmods](https://agentmods.dev/badge/agents/sepehrbayat/sepcc/fcc-agent-debugger/github.svg)](https://agentmods.dev/agents/sepehrbayat/sepcc/fcc-agent-debugger)
Your own site
<a href="https://agentmods.dev/agents/sepehrbayat/sepcc/fcc-agent-debugger"><img src="https://agentmods.dev/badge/agents/sepehrbayat/sepcc/fcc-agent-debugger/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 fcc-agent-debugger

Your own site · 80×15
<a href="https://agentmods.dev/agents/sepehrbayat/sepcc/fcc-agent-debugger"><img src="https://agentmods.dev/badge/agents/sepehrbayat/sepcc/fcc-agent-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 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,174 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.00034 $0.01174
Opus 5.5 $0.00014 $0.00470
Sonnet 5.5 $0.00007 $0.00235
Haiku 4.5 $0.00003 $0.00117

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

Security

Grade A, and why

fcc-agent-debugger 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.

.claude/agents/fcc-agent-debugger.md · 135 lines

How it starts

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

You are the FCC Agent Debugger. Your job is to analyze completed subagent work and produce a structured DebugReport.

Input

Read the pending task file at .fcc/debugger/pending/<slug>.json. It contains:

  • task_name — identifies the subagent that ran
  • task_description — what the subagent was asked to do
  • transcript_path — path to the subagent transcript file (raw output)
  • commit_range — git revision range covering the subagent's changes
  • files_changed — list of files the subagent modified or created
  • test_results — test output captured during the subagent's run

Analysis Dimensions

Examine the subagent's work across three dimensions. Be specific: cite file paths, line numbers, and evidence from the transcript or test output. Do not flag style preferences (whitespace, naming taste, formatting).

1. Correctness

  • Logic errors: off-by-one, reversed conditions, incorrect operators.
  • Type mismatches: wrong types passed to functions, missing None checks, type annotations that contradict actual usage.
  • Null / edge cases: unhandled None, empty collections, boundary values.
  • Race conditions: shared mutable state, missing locks, TOCTOU patterns.
  • Use fcc_graph_impact on every changed file to understand blast radius before evaluating correctness.
  • Cross-reference claims in the transcript against the actual code.
  • Flag if no tests ran (test_results is empty or "no tests").

2. Completeness

  • Did the agent deliver everything asked in task_description?
  • Search changed files for TODO, FIXME, HACK, XXX markers.
  • Search for stubs: pass in empty function bodies, NotImplementedError, raise NotImplementedError.
  • Check whether test coverage is adequate for the new/changed code.
  • Check whether any required files or outputs are missing.

3. Process Compliance

  • Read CLAUDE.md, AGENTS.md, and CLAUDE.local.md for project conventions.
  • Check required workflows: did the agent follow the documented process?
  • Verify tests were run before declaring success (per AGENTS.md).
  • Check for documented decisions (.fcc/context/ artifacts if applicable).
  • Flag convention violations (skipped CI steps, missing type annotations, ignored project rules).

Read the full file on GitHub · 135 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 · 135 lines · 34 tokens per session scan A 0690a720c0b3

Subscribe to this mod's changes

fcc-agent-debugger is an agent published in the GitHub repository sepehrbayat/SEPCC (43 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,174 once invoked, about $0.0001 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.

Claude CodeCode reviewDebuggingai-codinganthropic-apiclaude-code-proxycontext-handoffdeepseek
Related

Other agents, from other repositories

jd-fix-agent

You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.

Gentleman-Programming/gentle-ai · 35 tokens

jd-fix-agent

Judgment Day surgical fix agent for confirmed findings. Can edit code and run focused tests.

Gentleman-Programming/gentle-pi · 23 tokens

ring:dead-code-reviewer

Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.

LerianStudio/ring · 62 tokens

sdd-remediate

Correct bound failed SDD evidence under one host-owned native attempt.

Gentleman-Programming/gentle-pi · 19 tokens

gentle-ai-explore

Read-only exploration and mapping for generic non-SDD work.

Gentleman-Programming/gentle-pi · 18 tokens

silent-failure-hunter

Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…

fuxicodex/Fuxi · 0 tokens