Borrowing it
Nothing to install: this file belongs to alex-alecu/garden-desk. 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/alex-alecu/garden-desk/main/.agents/skills/garden-desk-fix-bug/SKILL.mdgit clone --depth 1 https://github.com/alex-alecu/garden-deskWrote 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/alex-alecu/garden-desk/garden-desk-fix-bug)<a href="https://agentmods.dev/skills/alex-alecu/garden-desk/garden-desk-fix-bug"><img src="https://agentmods.dev/badge/skills/alex-alecu/garden-desk/garden-desk-fix-bug/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/alex-alecu/garden-desk/garden-desk-fix-bug"><img src="https://agentmods.dev/badge/skills/alex-alecu/garden-desk/garden-desk-fix-bug.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.00045 | $0.00252 |
| Opus 5 | $0.00023 | $0.00126 |
| Sonnet 5 | $0.00009 | $0.00050 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
garden-desk-fix-bug 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 8d 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.
What it actually says
Fix A Garden Desk Bug
Top priority: add exactly one reproducing test and make the smallest fix. Do not add other code, tests, or verification.
- Reproduce the bug with source inspection, existing evidence, and the smallest deterministic test. For agent-loop behavior, use the real-model reproduction in the development workflow only as a last resort and only after explicit owner approval.
- Write one failing test that reproduces the bug in the existing test file for the module (create a file only if none exists). Run it and confirm it fails for the expected reason.
- Make the smallest fix. Run the test again and confirm it passes.
- Run
pnpm lintandpnpm typecheck. - Add no further tests and do not edit unrelated tests.
Report the root cause, the fix, and the exact commands and results. Do not commit or push unless asked.
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.
- 8d ago First seen · 17 lines · 45 tokens per session scan A adab7a09470f
garden-desk-fix-bug is a skill published in the GitHub repository alex-alecu/garden-desk (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 252 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
代码调试
A debugging workflow that reproduces a problem with a failing test, collects evidence, finds the underlying cause, applies a fix, and runs regression checks. Regression checks verify that the fix does not break behavior that already worked.
rpi-remediate
Validate and resolve every actionable pre-launch finding in ordered local waves with TDD, finding disposition and preservation of strategic exceptions.
pn-systematic-debugging
Root cause analysis with triage mode — Phase 0 feedback loop, investigate first, one question max, then isolate, hypothesize, confirm. Outputs TDD fix plan with RED-GREEN cycles; optional GitHub issue via GitHub MCP. Use when debugging a failure or bug.
pn-discipline-philosophy
Defines engineering discipline: test-first, root-cause before fix, minimal change, measure-before-optimize, review/second look, evidence over guess. Use when implementing features, debugging, planning, or establishing development practices. Aligns with TDD, systematic debugging, and RCA practices (current).
diagnose-hard-problem
Disciplined diagnosis loop for hard problems, diagnosing bugs and regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test.