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 skills add MeherBhaskar/temporal-debug-skill --skill temporal-debuggit clone --depth 1 https://github.com/MeherBhaskar/temporal-debug-skillWrote 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/meherbhaskar/temporal-debug-skill/temporal-debug)<a href="https://agentmods.dev/skills/meherbhaskar/temporal-debug-skill/temporal-debug"><img src="https://agentmods.dev/badge/skills/meherbhaskar/temporal-debug-skill/temporal-debug/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/meherbhaskar/temporal-debug-skill/temporal-debug"><img src="https://agentmods.dev/badge/skills/meherbhaskar/temporal-debug-skill/temporal-debug.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.00077 | $0.02071 |
| Opus 5.5 | $0.00031 | $0.00828 |
| Sonnet 5.5 | $0.00015 | $0.00414 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
temporal-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temporal Debug Skill
Goal
Help the user debug a bug by reconstructing the code state at the time the bug
occurred, rather than analyzing the current HEAD. This eliminates confusion
from recent unrelated changes.
When to Use
- User mentions a bug with a time reference: "3 hours ago", "last night", "yesterday's deploy", "this morning"
- User references a specific version: "v2.4.1", "release-2024-01", tag name
- User shares an error log with a timestamp
- User suspects a recent change introduced a bug but current code looks fine
- Deployment errors - user says "deploy failed" or "production is down" with a version/timestamp reference
When NOT to Use
- New feature development
- Refactoring without bug context
- Bug clearly in current code (user says "just broke after my last commit")
Workflow
1. Resolve the Target Commit
Extract temporal clues from the user's message and resolve to a commit hash:
| Clue Type | Git Command |
|---|---|
| Explicit commit hash | Use directly |
Git tag / version (e.g., v2.4.1) |
git rev-list -1 v2.4.1 |
| Relative time (e.g., "3 hours ago") | git log --before="3 hours ago" -1 --format="%H" |
| ISO date (e.g., "2024-01-15") | git log --before="2024-01-15" -1 --format="%H" |
| "last night" / "yesterday" | git log --before="yesterday 23:59" -1 --format="%H" |
For deployment errors:
- If user mentions a release version (e.g., "deploy of v2.4.1 failed"), use the tag
- If user mentions a branch (e.g., "release/v2.4 branch"), use the branch tip
- If user says "current production deploy", check if there's a
productionormainbranch deployed
If multiple conflicting clues, ask the user which to use. If user gives explicit commit hash, use it directly — no resolution needed.
Store the resolved hash as TARGET_COMMIT.
2. Create Isolated Historical Workspace
Create a git worktree at the target commit. This is read-only, isolated,
and doesn't touch the user's working directory.
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.
- 1mo ago First seen · 199 lines · 77 tokens per session scan A ad2ac70e22c5
temporal-debug is a skill published in the GitHub repository MeherBhaskar/temporal-debug-skill (6 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 2,071 once invoked, about $0.0003 per session on Opus 5.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
debug-my-harness
Diagnose why an agent harness misbehaved by reading the local flight-recorder ledger (.vigiles/runs.jsonl) — which skills fired or got hijacked, which hooks blocked or wrongly allowed, which subagent tool-contract violations happened, and how a skill's trigger rate moved. Use when asked why a skill stopped firing, why…
linter-docs
Deep linter reference for authoring or debugging a vigiles enforce() rule — plugin tables, AST selectors, type-aware rules, auto-fix, and edge cases for ESLint, Ruff, Pylint, RuboCop, Stylelint, and Clippy. Use when you need the exact rule name or config for a specific linter, not for running a linter. (JVM/Go linters…
debug
Fix bugs, crashes, errors, or failing tests. Use when "it's broken", "getting an error", "test is failing", or the cause isn't obvious.
explore
Answer "how does X work", "where is X defined", or "trace through Y" questions about a codebase using parallel subagent searches with cited summaries.
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…