Borrowing it
Nothing to install: this file belongs to ashaychangwani/imprint. 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/ashaychangwani/imprint/main/.agents/skills/debug-teach/SKILL.mdgit clone --depth 1 https://github.com/ashaychangwani/imprintWrote 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/ashaychangwani/imprint/debug-teach)<a href="https://agentmods.dev/skills/ashaychangwani/imprint/debug-teach"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/debug-teach/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/ashaychangwani/imprint/debug-teach"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/debug-teach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 40 Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.Fix: Remove unnecessary filesystem scanning. If file access is needed, use explicit, scoped paths. Avoid reading ~/.ssh, ~/.aws, or credential directories.
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.00039 | $0.01598 |
| Opus 5.5 | $0.00016 | $0.00639 |
| Sonnet 5.5 | $0.00008 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
debug-teach 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 2mo 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug an imprint teach run
Use this when a teach run failed, is stuck, was slow, or produced broken tools.
Step 1 — Determine what happened
Ask the user (or infer from context) which scenario applies:
| Scenario | Go to |
|---|---|
| Teach is currently running and looks stuck | Step 2a |
| Teach finished but tools are broken | Step 2b |
| Teach errored out | Step 2c |
| Teach was slow and user wants to know why | Use /imprint-teach-deepdive instead |
Step 2a — Stuck teach (still running)
Check what stage it's in:
# See if the compile-log is being written (growing = still compiling)
ls -la ~/.imprint/<site>/*/.compile-log.json
# Check if Chrome is still alive (replay/record stage)
pgrep -fl chromium || pgrep -fl chrome
# If tracing was on, check the last span
bun run scripts/analyze-phoenix.ts --kind teach --last 1
Common stuck points:
- Replay stage: browser hung waiting for a network response. Kill and re-run; check
IMPRINT_REPLAY_DEBUG=1output at/tmp/imprint-replay-debug-*.log - Compile agent looping: the agent is retrying a failing verification. Check the tail of
.compile-log.json - Shared module build: a module failed to verify and is retrying. Look for
pruningvsbuilt + verifiedin stderr
Step 2b — Teach finished but tools are broken
# Run audit to get a structured report
bun run src/cli.ts audit <site> --json
# Read the audit report
cat ~/.imprint/<site>/.audit-report.json | jq '{score, verdicts: [.verdicts[] | {tool: .tool, verdict: .verdict}]}'
# Read the compile agent's full conversation for a broken tool
cat ~/.imprint/<site>/<broken-tool>/.compile-log.json | jq '.[].role' | head -20
# Check the tool plan the agent was given
cat ~/.imprint/<site>/<broken-tool>/.tool-plan.md
# Test the playbook interactively
bun run src/cli.ts playbook <site> --headed --trace --param key=value
# Screenshots land at /tmp/imprint-playbook-<tool>-step<N>-<ts>.png
Step 2c — Teach errored out
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.
- 2mo ago First seen · 158 lines · 39 tokens per session scan A 18622c9b37f8
debug-teach is a skill published in the GitHub repository ashaychangwani/imprint (24 stars, last pushed 15d ago), licensed MIT. It adds 39 tokens to every session and 1,598 once invoked, about $0.0002 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-30.
Other skills, from other repositories
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
gini-bug-report
File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.
investigate
A structured root-cause investigation method for software bugs. It moves from history and reproduction through tested hypotheses, a focused fix, verification, and a report.
bugfix-triage
A method for locating the cause of a bug before changing code, using a minimal reproduction and step-by-step narrowing of the failing input and code path.
rust-native-scanner
Expertise in high-performance native codebase scanning and validation using Rust. Trigger this skill when asked to "scan the codebase natively", "run rust scanner", or "validate bxc core using rust".
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.