systematic-debugging

A command for investigating evaluation failures by tracing them to their underlying cause and applying a fix.

In plain words
What is it for?
Use it when tests, benchmarks, or other evaluations fail and you need to find and fix the root problem.
Why use it?
It provides a defined approach for failures instead of making changes based only on surface symptoms.

Command

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.

agentmods
npx agentmods add commands/ibrahim-3d/orchestrator-supaconductor/systematic-debugging
Clone the repo
git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 56 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00015 $0.00056
Opus 5 $0.00008 $0.00028
Sonnet 5 $0.00003 $0.00011
Haiku 4.5 $0.00002 $0.00006

Measured 2d ago against content hash f1067d017057, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

systematic-debugging 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.

commands/systematic-debugging.md · 9 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 2d ago First seen · 9 lines · 15 tokens per session scan A f1067d017057

Subscribe to this mod's changes

systematic-debugging is a command published in the GitHub repository Ibrahim-3d/orchestrator-supaconductor (375 stars, last pushed 4mo ago), licensed AGPL-3.0. It adds 15 tokens to every session and 56 once invoked, about $0.0001 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.

Related

Other commands, from other repositories

culture-onboarding-90

Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…

frankxai/Starlight-Intelligence-System · 101 tokens

org-reorg-trauma-audit

Pre-reorg trauma audit and sequencing plan. Opens with the 70%+ reorg-failure honesty, runs trauma history + threat-activation forecast (SCARF), produces a wave-based sequencing plan, communication architecture grounded in Kotter + Bridges, per-team mitigation, and post-reorg Talent IS monitoring cadence. Refuses…

frankxai/Starlight-Intelligence-System · 100 tokens

perf-conflict-mediation

Psychologist-grade conflict mediation between two parties. Produces 90-minute mediation session structure — separate prep with each party (each three-conversations narrative collected privately) + joint session structure with psychological safety design + commitments + follow-up. Names what to escalate to professional…

frankxai/Starlight-Intelligence-System · 95 tokens

perf-difficult-conversation

Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…

frankxai/Starlight-Intelligence-System · 93 tokens

design-regimen

Design an integrated weekly regimen — training, nutrition, sleep, stress, recovery — matched to the person's actual life. Composes with gym-training-expert and health-nutrition-expert for domain detail. Produces a sustainable architecture, not an extreme program. Not medical advice.

frankxai/Starlight-Intelligence-System · 60 tokens

hire-calibrate

Run the pre-loop calibration session — 60 minutes with ≥3 raters, review the rubric, score 2 anchor candidates the team has previously seen, surface inter-rater drift, agree on hire-bar examples. The calibration session itself is the deliverable. Without it, the loop runs on uncalibrated rulers. Per Project Oxygen …

frankxai/Starlight-Intelligence-System · 86 tokens