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 bug-ops/zeph --skill code-analysisgit clone --depth 1 https://github.com/bug-ops/zephWrote 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/bug-ops/zeph/code-analysis)<a href="https://agentmods.dev/skills/bug-ops/zeph/code-analysis"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/code-analysis/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/bug-ops/zeph/code-analysis"><img src="https://agentmods.dev/badge/skills/bug-ops/zeph/code-analysis.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 Prompt Injection · line 55 Subtle instructions detected that may alter agent decision-making or introduce hidden biases.Fix: Review content for implicit steering or bias. Ensure instructions are explicit and align with the skill's stated purpose.
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.00105 | $0.02172 |
| Opus 5.5 | $0.00042 | $0.00869 |
| Sonnet 5.5 | $0.00021 | $0.00434 |
| Haiku 4.5 | $0.00011 | $0.00217 |
Grade A, and why
code-analysis 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Analysis with LSP
Use LSP tools for accurate, compiler-verified code understanding. These tools require the mcpls
MCP server to be configured.
Positions
Positions are 1-based: line 1, column 1 is the first character. If you read a file and see line numbers in the output, use those directly — no conversion needed (mcpls translates to 0-based LSP positions internally).
File paths must be absolute. Relative paths will not resolve correctly.
Tool Reference
Code Intelligence
| Tool | Purpose | When to use |
|---|---|---|
get_hover |
Type signature, inferred type, and documentation at a position | "What type is X?", "What does this function do?" |
get_definition |
Navigate to where a symbol is defined | Read a function/type implementation before reasoning about it |
get_references |
Find all usages of a symbol across the workspace | Before renaming, deleting, or changing a symbol's signature |
get_completions |
Context-aware suggestions respecting types and scope | Exploring unknown APIs, discovering available methods |
get_document_symbols |
Structured outline of a file (functions, types, constants, fields) | Understanding file structure without reading every line |
workspace_symbol_search |
Search for a symbol by name across the entire workspace | Know a name but not which file defines it |
Diagnostics and Correctness
| Tool | Purpose | When to use |
|---|---|---|
get_diagnostics |
Real compiler errors and warnings for a file | After editing code — always call to verify correctness |
get_cached_diagnostics |
Previously cached diagnostics (no fresh check) | Quick check when file has not changed recently |
get_code_actions |
Quick fixes, refactorings, source actions at a position | Fix diagnostics automatically, add missing imports |
Refactoring
| Tool | Purpose | When to use |
|---|---|---|
rename_symbol |
Workspace-wide rename with full reference tracking | Always prefer over manual find-and-replace |
format_document |
Apply language-specific formatting rules | After editing, before committing |
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 · 200 lines · 105 tokens per session scan A 21c3c46ecd01
code-analysis is a skill published in the GitHub repository bug-ops/zeph (65 stars, last pushed 11d ago), licensed MIT. It adds 105 tokens to every session and 2,172 once invoked, about $0.0004 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
simplicio-dev-cli
Perform deterministic Simplicio code changes and validation through the Dev CLI. Use for file edits, patches, implementation, formatting, tests, diagnostics, pre-effect validation, retries, evidence files, and safe mutation workflows. The agent decides intent; Dev CLI owns the mutation and verification.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
optimization
Use when improving performance, latency, throughput, memory usage, or general efficiency. Start by defining target metrics, measuring comprehensively, attributing bottlenecks, validating with static analysis, and prioritizing macro-optimizations before micro-optimizations.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.