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 skills/shaymanor/hindsight/hindsight-debugnpx skills add ShayManor/Hindsight --skill hindsight-debuggit clone --depth 1 https://github.com/ShayManor/HindsightWrote 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/shaymanor/hindsight/hindsight-debug)<a href="https://agentmods.dev/skills/shaymanor/hindsight/hindsight-debug"><img src="https://agentmods.dev/badge/skills/shaymanor/hindsight/hindsight-debug.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.00054 | $0.00381 |
| Opus 5 | $0.00027 | $0.00191 |
| Sonnet 5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
hindsight-debug 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.
What it actually says
Debugging with Hindsight
When an error resists your parametric knowledge, query the shared corpus before guessing.
- Search. Call
search_errorwith:trace: the full stack trace / multi-line error, verbatim.message: the headline error (e.g.ImportError: undefined symbol).attempt_summary: one sentence on what you were doing ("Tried to build flash-attention 2.3.6 on Ubuntu 22.04 with torch 2.1 + CUDA 12.1").env:{cuda, os, arch, packages}when known — this conditions and ranks results.
- Read the top results. Each carries
why(matched frames, env match, and attempts/successes/success_rate) plussourceattribution. Prefer solutions with a higher success_rate. - Get the full record. Call
get_solution(id)for the chosen result — it includessolution_body,solution_code, and the exactrepro_script. - Try the fix.
- Always report back. Call
report_attempt(id, worked)withworked=trueorworked=false. Failures are the most valuable signal — they tell the commons which popular fixes do not actually work. Addnotesexplaining what differed.
Attribution: results may be licensed CC-BY-SA (Stack Overflow) or MIT. Preserve source.author/source.url if you quote a solution.
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 · 21 lines · 54 tokens per session scan A 99863b1d0837
hindsight-debug is a skill published in the GitHub repository ShayManor/Hindsight (2 stars, last pushed 16d ago), licensed BSD-2-Clause. It adds 54 tokens to every session and 381 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…