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/cfircoo/claude-code-toolkit/fullstack-qa-debuggergit clone --depth 1 https://github.com/cfircoo/claude-code-toolkitWhat 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.00045 | $0.00931 |
| Opus 5 | $0.00023 | $0.00465 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
fullstack-qa-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 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.
What it actually says
<react_grab_integration> Fast Element Context Extraction using react-grab (https://github.com/aidenybai/react-grab):
How it works:
- User hovers over any UI element in browser
- User presses Cmd+C (Mac) or Ctrl+C (Windows)
- Clipboard contains: filename, component name, HTML source
This makes debugging 3x faster than manual file exploration.
When user provides react-grab context, parse into:
interface ReactGrabContext {
html: string;
componentName: string;
filePath: string;
line: number;
}
</react_grab_integration>
<validation_checklist> Data Integrity:
- API endpoints return valid data
- Response shapes match TypeScript interfaces
- Null/undefined values handled gracefully
- Date/time formats parse correctly
UI Rendering:
- All components render without errors
- Loading states display during fetch
- Empty states show appropriate message
- Error states are user-friendly
Edge Cases:
- Empty data arrays show empty state
- Long text truncates appropriately
- Large numbers format correctly
- Missing optional fields don't break UI
Performance:
- Initial load < 3 seconds
- API calls don't block UI
- No unnecessary re-renders </validation_checklist>
<validation_report_schema>
interface ValidationReport {
passed: boolean;
timestamp: string;
summary: {
total_checks: number;
passed_checks: number;
failed_checks: number;
warnings: number;
};
categories: {
data_integrity: CheckResult[];
ui_rendering: CheckResult[];
edge_cases: CheckResult[];
performance: CheckResult[];
};
issues: Issue[];
recommendations: string[];
}
interface Issue {
severity: 'critical' | 'major' | 'minor' | 'info';
category: string;
description: string;
location: { file: string; line?: number };
suggested_fix: {
description: string;
code_change?: { old: string; new: string };
};
auto_fixable: boolean;
}
</validation_report_schema>
<output_location> Write validation results to: .fullstack-state/knowledge-base.json (update validation field) </output_location>
<testing_commands>
# TypeScript compilation
npx tsc --noEmit
# Lint check
npx eslint src/ --ext .ts,.tsx
# Build verification
npm run build
</testing_commands>
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 · 163 lines · 45 tokens per session scan A 9b7350e08e62
fullstack-qa-debugger is an agent published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 931 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.