Borrowing it
Nothing to install: this file belongs to aviatesk/JETLS.jl. 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/aviatesk/JETLS.jl/master/.agents/skills/zed-agent-diagnostics/SKILL.mdgit clone --depth 1 https://github.com/aviatesk/JETLS.jlWrote 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/aviatesk/jetls.jl/zed-agent-diagnostics)<a href="https://agentmods.dev/skills/aviatesk/jetls.jl/zed-agent-diagnostics"><img src="https://agentmods.dev/badge/skills/aviatesk/jetls.jl/zed-agent-diagnostics.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.1 | $0.00053 | $0.00576 |
| Opus 5 | $0.00026 | $0.00288 |
| Sonnet 5 | $0.00011 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
zed-agent-diagnostics 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 6d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zed agent diagnostics
Use this skill when you are running as Zed's built-in coding agent in this
repository and need to satisfy project instructions that require jetls check
or ./scripts/selfcheck.sh.
Validation rule
When project instructions say to run jetls check or ./scripts/selfcheck.sh
after modifying code, normally satisfy that requirement by using Zed's
diagnostics tool instead of running the terminal command. Prefer it when
available because it is usually faster than starting a separate selfcheck.
Use Zed diagnostics for the initial check. Run ./scripts/selfcheck.sh only
when diagnostics cannot provide enough confidence.
How to use diagnostics
- After code edits, call the diagnostics tool for the project.
- If the changed files are known and targeted diagnostics are useful, also call the diagnostics tool for those files.
- Treat diagnostics in files you edited as issues to fix when they are likely caused by your changes.
- Do not remove or simplify meaningful code only to silence diagnostics. If a natural fix is difficult to find, explain the situation and ask the user for help.
- If diagnostics appear unrelated to your changes, report them as pre-existing or unrelated instead of fixing them opportunistically.
When diagnostics may be unreliable
JETLS analyzes itself through a Revise-based server session. This is efficient, but changes to type definitions or global bindings may not be fully reflected in the running session. Zed diagnostics can therefore be stale, incomplete, or fail.
Be especially conservative when changes affect type definitions, macros,
include structure, diagnostics infrastructure, or code that diagnostics
itself depends on. If diagnostics code was edited, diagnostics may be broken
by the current changes.
If diagnostics look stale, incomplete, or broken, do not spend time on server
restart loops. Explain that Zed diagnostics do not provide enough confidence and
run ./scripts/selfcheck.sh to get a fresh check, unless the user has asked not
to run it.
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.
- 6d ago First seen · 65 lines · 53 tokens per session scan A db413bd786d6
zed-agent-diagnostics is a skill published in the GitHub repository aviatesk/JETLS.jl (306 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 576 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-30.
Other skills, from other repositories
health-check
Get an overall Python code quality health score using pyscn. Use when user asks how healthy or good the code is, wants a quality overview, a grade, a summary of technical debt, or a before/after quality comparison.
bloat-detector
Detects codebase bloat via dead code, duplication, complexity, and doc bloat scans. Use when codebase feels large or before a release.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
fix-ci
Fix CI failures and performance regressions for a Julia package PR by iterating - triage the latest CI results, fix one root cause, verify locally, push. Use when a PR's GitHub Actions or Buildkite CI is failing, or when CI jobs run slower than they do on the main branch. Verifies CPU and GPU compilation locally…
codeql-expert
Expert-level CodeQL for static analysis, vulnerability detection, and security code scanning. Use when the user mentions static analysis, SAST, vulnerability detection, or github security, or when the task involves writing CodeQL queries, building a CodeQL database, taint tracking, or scanning for injection and…