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 skills add synaptiai/agent-capability-standard --skill debug-workflowgit clone --depth 1 https://github.com/synaptiai/agent-capability-standardWrote 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.
[](https://agentmods.dev/skills/synaptiai/agent-capability-standard/debug-workflow)<a href="https://agentmods.dev/skills/synaptiai/agent-capability-standard/debug-workflow"><img src="https://agentmods.dev/badge/skills/synaptiai/agent-capability-standard/debug-workflow/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.
<a href="https://agentmods.dev/skills/synaptiai/agent-capability-standard/debug-workflow"><img src="https://agentmods.dev/badge/skills/synaptiai/agent-capability-standard/debug-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.02317 |
| Opus 5.5 | $0.00014 | $0.00927 |
| Sonnet 5.5 | $0.00007 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
debug-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent
Run the composed workflow debug-workflow using atomic capability skills to systematically debug code changes with full safety and audit capabilities.
Success criteria:
- Every step output is grounded with evidence anchors
- Safety gates are respected (checkpoint before any mutation)
- All issues are traced to root cause with supporting evidence
- Final result includes complete audit trail
- Rollback pathway documented and verified
Compatible schemas:
reference/workflow_catalog.yaml
Inputs
| Parameter | Required | Type | Description |
|---|---|---|---|
goal |
Yes | string | The debugging objective (e.g., "identify why tests fail after refactor") |
scope |
Yes | string|array | Files, directories, or components to investigate |
constraints |
No | object | Hard limits (e.g., time budget, files to exclude, severity threshold) |
prior_context |
No | object | Previous debugging attempts or known information |
Procedure
-
Create checkpoint marker if mutation might occur:
- Create
.claude/checkpoint.okafter confirming rollback strategy
- Create
-
Invoke
/inspectand store output asinspect_out- Examine the scope for symptoms, error patterns, recent changes
-
Invoke
/searchand store output assearch_out- Find related code, error messages, similar patterns
-
Invoke
/map-relationshipsand store output asmap-relationships_out- Map dependencies, call graphs, data flows
-
Invoke
/model-schemaand store output asmodel-schema_out- Model the expected vs actual behavior
-
Invoke
/critiqueand store output ascritique_out- Critically analyze hypotheses, identify weak points
-
Invoke
/planand store output asplan_out- Create remediation plan with verification criteria
-
Invoke
/act-planand store output asact-plan_out- Execute the fix with checkpoint protection
-
Invoke
/verifyand store output asverify_out- Confirm fix addresses root cause
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 293 lines · 35 tokens per session scan A 06fc6dc59365
debug-workflow is a skill published in the GitHub repository synaptiai/agent-capability-standard (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 2,317 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-31.
Other skills, from other repositories
deep-code-review
Use when reviewing current branch for bugs before pushing or merging, when wanting a thorough multi-agent review of local changes, or when preparing work for human review.
sodam-harness-self-check
A self-checking instruction set for an AI agent. It tells the agent to verify important work, show evidence, and clearly disclose anything it could not check.
sodam-loop-repair
A Bash safety rule requiring every Bash call to include a timeout calculated from validation settings, with a stated default of 300000 milliseconds. Bash is a command-line shell used to run scripts and commands.
sodam-loop-status
A self-check command for SoDamLoop, a software system with safety components. It checks whether those components are still working normally.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…