specsfy-specialist-debugging

specsfy-specialist-debugging is a skill for Codex from promovaweb/specsfy. It costs 60 tokens per session (341 once invoked), scanned A, original, no licence file.

A debugging guide for finding the cause of bugs, regressions, intermittent failures, and performance problems. It uses reproduction, reducing a problem to a smaller case, hypotheses, and instrumentation such as extra measurements or logs.

In plain words
What is it for?
Use it to reproduce failures, narrow down their causes, test explanations, add measurements, and investigate bugs, regressions, intermittent issues, or slow behavior.
Why use it?
It helps investigate what is actually broken before changing code. It separates diagnosis from implementation when the user only asks for an explanation of the problem.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to reproduce failures, narrow down their causes, test explanations, add measurements, and investigate bugs, regressions, intermittent issues, or slow behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/promovaweb/specsfy/specsfy-specialist-debugging
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.

Any agent
npx skills add promovaweb/specsfy --skill specsfy-specialist-debugging
Clone the repo
git clone --depth 1 https://github.com/promovaweb/specsfy

Made for: Codex.

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 specsfy-specialist-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/promovaweb/specsfy/specsfy-specialist-debugging/github.svg)](https://agentmods.dev/skills/promovaweb/specsfy/specsfy-specialist-debugging)
Your own site
<a href="https://agentmods.dev/skills/promovaweb/specsfy/specsfy-specialist-debugging"><img src="https://agentmods.dev/badge/skills/promovaweb/specsfy/specsfy-specialist-debugging/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 specsfy-specialist-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/promovaweb/specsfy/specsfy-specialist-debugging"><img src="https://agentmods.dev/badge/skills/promovaweb/specsfy/specsfy-specialist-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 341 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 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.1 $0.00060 $0.00341
Opus 5 $0.00030 $0.00170
Sonnet 5 $0.00012 $0.00068
Haiku 4.5 $0.00006 $0.00034

Measured 10d ago against content hash 270a6132a446, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

specsfy-specialist-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 10d 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.

example/.agents/skills/specsfy-specialist-debugging/SKILL.md · 37 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Files

What ships with it

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

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. 10d ago First seen · 37 lines · 60 tokens per session scan A 270a6132a446

Subscribe to this mod's changes

specsfy-specialist-debugging is a skill published in the GitHub repository promovaweb/specsfy (77 stars, last pushed yesterday), with no licence file. It adds 60 tokens to every session and 341 once invoked, about $0.0003 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 skills, from other repositories

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

adk-debug

Diagnoses misbehaving ADK agents by inspecting sessions, events, tool calls, and the exact request that reached the model. Covers the adk run CLI and the adk web dev server with its session, trace, and debug HTTP endpoints. Use when an agent returns the wrong answer, ignores a tool or swallows a tool error, hangs…

google/adk-python · 191 tokens

typescript-testing

Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.

ComposioHQ/composio · 65 tokens

cli-e2e

Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.

ComposioHQ/composio · 62 tokens

potpie-cli

Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, search, graph workbench reads/writes, and pot scope behavior.

potpie-ai/potpie · 50 tokens

rubber-duck

Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…

kirodotdev/KiroCrew · 161 tokens