Borrowing it
Nothing to install: this file belongs to membrane/api-gateway. 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/membrane/api-gateway/master/.claude/skills/config-error-handling/SKILL.mdgit clone --depth 1 https://github.com/membrane/api-gatewayWrote 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/membrane/api-gateway/config-error-handling)<a href="https://agentmods.dev/skills/membrane/api-gateway/config-error-handling"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/config-error-handling/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/membrane/api-gateway/config-error-handling"><img src="https://agentmods.dev/badge/skills/membrane/api-gateway/config-error-handling.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.00089 | $0.00937 |
| Opus 5.5 | $0.00036 | $0.00375 |
| Sonnet 5.5 | $0.00018 | $0.00187 |
| Haiku 4.5 | $0.00009 | $0.00094 |
Grade A, and why
config-error-handling 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Error Handling
Two failure phases, two reporting paths
Membrane config errors surface differently depending on when they're thrown, and that's the first thing to get right.
Setter-time — inside an @MCAttribute/@MCChildElement setter, during YAML property binding
(annot/.../yaml/parsing/binding/PropertyBinder.java, populate()). That catch (Throwable cause)
re-wraps into new ConfigurationParsingException(cause.getMessage()) and attaches a
ParsingContext (source location), so RouterCLI renders a highlighted > YAML snippet pointing
at the offending line. Mind the message: reflection wraps a setter's own exception in
InvocationTargetException, and PropertyBinder does not unwrap it, so the message it copies is
the wrapper's (null) — the real text sits in cause.getCause().getMessage(). The
@MCElement(collapsed=true) scalar path in ObjectBinder does unwrap (e.getTargetException()).
Example: WsuTimestampInterceptor.setTtl (core/.../soap/wsse/WsuTimestampInterceptor.java)
catches DateTimeParseException from Duration.parse and rethrows a ConfigurationException
with a concrete valid-example ("PT5M").
Init-time — inside interceptor.init(Router), reached via DefaultRouter.init() →
AbstractRouter.initProxies() → proxy.init(this), i.e. after all YAML parsing has finished.
The YAML bootstrap does carry a ParsingContext into the bean registry, but nothing on this
initProxies() path passes it on, so an interceptor's init() has no source location to report —
not fixable per-interceptor without a cross-cutting change to plumb it through Router/interceptor
init.
ConfigurationException thrown here is caught by
SpringConfigurationErrorHandler.handleConfigurationException
(core/.../exceptions/SpringConfigurationErrorHandler.java:128), which prints a plain
"************** Configuration Error ***..." / "Reason: <cause message>" block — no YAML
snippet. This is the existing, accepted behavior for every interceptor's init()-time checks
(missing keystore, bad key alias, unsupported algorithm, ...), not a bug to chase per class.
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 · 62 lines · 89 tokens per session scan A f813343e595a
config-error-handling is a skill published in the GitHub repository membrane/api-gateway (656 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 937 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-09-05.
Other skills, from other repositories
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
fastapi-expert
Expert-level FastAPI development for high-performance Python APIs with async support. Use when the user mentions Python, API, async, REST, OpenAPI, or Pydantic, or when the task involves FastAPI Features.
openapi-expert
Expert-level OpenAPI/Swagger specification for API design, documentation, and code generation. Use when the user mentions swagger, API specs, REST, API design, or documentation, or when the task involves OpenAPI Specification, Webhooks, or Polymorphism.
construtor-de-api
Construção e documentação de APIs REST e GraphQL: design de endpoints, versionamento, autenticação, tratamento de erros, documentação OpenAPI 3.0 e boas práticas de segurança e performance.
api-design-patterns
Design robust APIs with RESTful patterns, GraphQL schemas, versioning strategies, and error handling conventions. Supports OpenAPI/Swagger documentation and SDK generation patterns. Triggers on API design, schema definition, endpoint architecture, or developer experience requests.
api-design
Design REST API contracts that are consistent, evolvable, and easy to consume.