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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill post-fix-tracegit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/post-fix-trace)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/post-fix-trace"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/post-fix-trace/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/post-fix-trace"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/post-fix-trace.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.00118 | $0.02600 |
| Opus 5.5 | $0.00047 | $0.01040 |
| Sonnet 5.5 | $0.00024 | $0.00520 |
| Haiku 4.5 | $0.00012 | $0.00260 |
Grade A, and why
post-fix-trace 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 12d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Fix Regression Trace
After you fix a bug, you've changed the system. That change might fix the original problem and quietly break something else: a calculation that stops recomputing, a field that is no longer persisted, a query that now includes soft-deleted records, a new main-thread bottleneck. The first trace found the disease; this trace checks whether the surgery nicked an artery.
When This Runs
This skill activates after a fix is applied: after the fix gate of your debug workflow, after the fix phase of systematic debugging, or after any bug-fix commit. It runs before the debug session is considered complete. A fix that hasn't been traced for side effects is not yet done.
Precondition: is the debug session actually done?
Check whether the user is still providing diagnostic input. If they are pasting logs, sharing crash reports, describing new symptoms, or asking questions about the bug, the session is still active and your fix is a hypothesis. Don't run this yet. Wait for them to finish, or ask: "Are there more symptoms to look at before I verify this fix?"
Treating a single fix commit as final while the user is mid-paste on crash logs is a common failure: more fixes usually follow, and anything shipped in between is built on a provisional diagnosis.
The Second Trace
Step 1: Map the blast radius
Read the diff of the fix. For every changed line, answer:
- What else calls this code? Trace callers up: which views, view models and services call the function you changed?
- What does this code feed into? Trace callees down: if you changed how a value is calculated, where is it displayed, persisted, exported, aggregated?
- What shares state with this code? Look for shared mutable state: the same context object, singleton, observable property, or stored record type.
Write the blast radius as a list of file:line references. Not "various views use this" - name them.
Step 2: Check each blast radius path
For each path from Step 1, verify the fix didn't break it. Check:
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.
- 12d ago First seen · 181 lines · 118 tokens per session scan A 7cf1ecf665c5
post-fix-trace is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 118 tokens to every session and 2,600 once invoked, about $0.0005 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-10-15.
Other skills, from other repositories
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
agent-incident-postmortem
Run a blameless postmortem for an incident caused by an AI agent or LLM feature — hallucinated facts shipped to users, runaway tool use, prompt injection, cost blowouts, or wrong actions taken autonomously. Use when asked to write up an AI incident, analyse why an agent did something wrong, or produce corrective…
agent-design-review
Review an LLM agent design and find where it will be unreliable, expensive, or unsafe. Use when asked to review an agent architecture, critique a multi-step/tool-using agent, debug an agent that loops or goes off-task, or harden an agent before launch. Produces a structured review — task fit, control flow, tools…
prompt-debugging
Figure out why a prompt isn't working and fix it — diagnose the actual failure (ambiguity, missing context, wrong format, conflicting instructions) instead of randomly rewording. Use when asked why isn't my prompt working, the AI keeps ignoring my instructions, my prompt gives inconsistent results, or how do I fix…
prompt-optimizer
Diagnose and rewrite an underperforming LLM prompt so it produces reliable, well-structured output. Use when asked to improve a prompt, fix a prompt that gives inconsistent or wrong results, reduce hallucination/refusals, or make output follow a format. Produces a rewritten prompt with a diagnosis of what was failing…
rag-architecture-review
Review an existing Retrieval-Augmented Generation system and find why it underperforms. Use when asked to review or audit a RAG pipeline, diagnose wrong/ungrounded answers from a 'chat with your docs' feature, or improve an already-built knowledge assistant. Produces a staged review — ingestion, chunking, retrieval…