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 hugobowne/show-us-your-agent-skills --skill try-exceptgit clone --depth 1 https://github.com/hugobowne/show-us-your-agent-skillsWrote 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/hugobowne/show-us-your-agent-skills/try-except)<a href="https://agentmods.dev/skills/hugobowne/show-us-your-agent-skills/try-except"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/try-except/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/hugobowne/show-us-your-agent-skills/try-except"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/try-except.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.03461 |
| Opus 5 | $0.00023 | $0.01731 |
| Sonnet 5 | $0.00009 | $0.00692 |
| Haiku 4.5 | $0.00005 | $0.00346 |
Grade A, and why
try-except scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Network calls (`requests.get()`, `socket.connect()`, `urllib.urlopen()`) How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project: honnibal/claude-skills. "Claude skills I'm experimenting with. Please review carefully before use."
License: MIT License. Full license text is in
LICENSEalongside this file.Snapshot: Frozen copy of
try-except.md.txtas of 2026-05-22. The maintained version lives upstream and may have evolved since this snapshot.
Interrogate Try/Except Usage
You are now in try/except audit mode. Your job is to read Python source files,
find every try/except block, and evaluate whether each one is correctly
scoped, catches the right exceptions, and doesn't mask bugs.
The guiding principle: context determines whether try/except or a conditional
check is appropriate. Try/except is for external state you cannot control —
filesystem, network, concurrent access — where race conditions make precondition
checks unreliable. For conditions over local values, use if, in, hasattr,
or similar checks instead.
Built-in exceptions like KeyError, AttributeError, TypeError, and
IndexError are fire escapes — emergency exits that tell you a bug has
occurred. Catching them indiscriminately is stacking old furniture in the fire
escape: harmless until a real emergency, then fatal.
Scope
$ARGUMENTS
- If the user names specific files or directories, scope your work to those.
- If no argument is given, work through the Python files in the current project.
- For large codebases, use
AskUserQuestionto let the user choose which modules or packages to start with. Don't try to do everything at once.
Workflow
-
Find all try/except blocks. Grep for
try:across the files in scope. Read each file that contains them. -
Classify each block. For every try/except, work through the analysis checklist below. Take notes before proposing any changes — you need to understand what each statement in the try block does and where exceptions might actually come from.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 357 lines · 47 tokens per session scan A c4911f0c3e08
try-except is a skill published in the GitHub repository hugobowne/show-us-your-agent-skills (67 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 3,461 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.