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/tibsfox/gsd-skill-creator/gsd-debuggergit clone --depth 1 https://github.com/Tibsfox/gsd-skill-creatorWrote 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/agents/tibsfox/gsd-skill-creator/gsd-debugger)<a href="https://agentmods.dev/agents/tibsfox/gsd-skill-creator/gsd-debugger"><img src="https://agentmods.dev/badge/agents/tibsfox/gsd-skill-creator/gsd-debugger.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00072 |
| Opus 5 | $0.00000 | $0.00036 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
gsd-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 4d 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.
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.
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.
- 4d ago First seen · 7 lines · 0 tokens per session scan A 8e2d4575a147
gsd-debugger is an agent published in the GitHub repository Tibsfox/gsd-skill-creator (69 stars, last pushed 1mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 72 tokens. 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
orchestrator
Multi-phase development agent. Research > Plan > Implement with validation gates. Use PROACTIVELY when building features that touch >5 files or require architecture decisions.
planner
Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements.
data-engineer
Data specialist — SQL correctness, query performance, schema design, dbt models, pipeline reliability (Airflow / Dagster / Prefect / Fivetran). Use for query review, index planning, migration review, dbt model patterns, and pipeline idempotency.
threat-modeler
Structured threat modeling over a diff, a component, or a proposed feature. Walks STRIDE (or LINDDUN for privacy-heavy work) and produces an actionable threat list with mitigations. Use when the task is "what could go wrong here" at the design level, not "is this line safe" (that's @security-reviewer).
code-reviewer
Staff-level PR review of the current diff or a specified ref. Use when the user asks for "a review", "a second opinion", or runs /holocron:review. Reviews for correctness, clarity, test quality, and blast radius.
perf-engineer
Performance analysis — Core Web Vitals on the frontend, N+1 and index gaps on the backend, bundle size deltas, rendering cost. Use when the task mentions "slow", "too big", "regression", or /holocron:perf runs.