Borrowing it
Nothing to install: this file belongs to justinz12xd/HACKATON-TAWS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/justinz12xd/HACKATON-TAWS/main/.agents/skills/jelou-debug-conversation/SKILL.mdgit clone --depth 1 https://github.com/justinz12xd/HACKATON-TAWSWrote 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/justinz12xd/hackaton-taws/jelou-debug-conversation)<a href="https://agentmods.dev/skills/justinz12xd/hackaton-taws/jelou-debug-conversation"><img src="https://agentmods.dev/badge/skills/justinz12xd/hackaton-taws/jelou-debug-conversation/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/justinz12xd/hackaton-taws/jelou-debug-conversation"><img src="https://agentmods.dev/badge/skills/justinz12xd/hackaton-taws/jelou-debug-conversation.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.00173 | $0.06386 |
| Opus 5 | $0.00086 | $0.03193 |
| Sonnet 5 | $0.00035 | $0.01277 |
| Haiku 4.5 | $0.00017 | $0.00639 |
Grade A, and why
jelou-debug-conversation 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 9d 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 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.
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.
- 9d ago First seen · 553 lines · 173 tokens per session scan A 1cbb5c6e7f71
jelou-debug-conversation is a skill published in the GitHub repository justinz12xd/HACKATON-TAWS (2 stars, last pushed 1mo ago), with no licence file. It adds 173 tokens to every session and 6,386 once invoked, about $0.0009 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-31.
Other skills, from other repositories
spec-code-review
Structured code review for bugs, regressions, tests, and standards. Report-only by default; apply fixes only when the current user or upstream caller explicitly requests review-and-fix. mode:agent is always report-only.
spec-compound-refresh
Refresh docs/solutions learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless docs/solutions is explicit.
spec-debug
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
spec-simplify-code
Simplify recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use for tidy/refactor passes; use spec-debug for bugs.
spec-explain
Create a durable, visual teaching artifact for a concept, diff, idea, or recent-work window, with an optional check-in that makes it stick. Use when the user asks to be taught or wants a deep explainer; not for ordinary Q&A, brief why-followups, diagnosis, status updates, or concise trade-off answers.
procurement-analysis
A procurement analysis workflow for breaking down purchasing needs, collecting data, analysing it, making charts, and writing a report. It covers supplier comparisons, price analysis, material selection, and procurement strategy reviews.