Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. 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/PackmindHub/packmind/main/packages/.github/instructions/packmind-domain-error-handling.instructions.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/instructions/packmindhub/packmind/packmind-domain-error-handling)<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-domain-error-handling"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-domain-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/instructions/packmindhub/packmind/packmind-domain-error-handling"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-domain-error-handling.svg" alt="Reviewed on agentmods" width="80" 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.00503 | $0.00503 |
| Opus 5.5 | $0.00201 | $0.00201 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
packmind packmind-domain-error-handling.instructions.md 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.
What it actually says
Standard: Domain Error Handling
Failures raised by a use case are answered centrally by DomainExceptionFilter, which maps them to an HTTP status and a log level. A failure carrying no kind reaches Nest's ExceptionsHandler as a... :
- Classify a third-party HTTP failure from
error.response?.statusand its headers; never derive a status from a substring oferror.message. - Extend
PackmindInternalErrorfor broken invariants the caller cannot correct. - Give each package one base per error family it raises — domain, internal, upstream — each with a literal
reasonunion and a typedcontext. - Never add an upstream kind to
DomainErrorKind:upstream_rate_limitedanswers 429 and stays anUpstreamError, because the axis is fault, not status class. - Never log an error you rethrow: the filter records every thrown failure once, with its level, stack and typed
context. - Never map domain errors in a controller with
instanceofand a NestHttpException; the filter mapskindcentrally. - Never throw
new Error(...)from a use case; throw a class extending the package'sDomainError,PackmindInternalErrororPackmindUpstreamErrorbase. - Pass
retryAfterSecondson an upstream throttle when the provider said how long; the filter emits it as theRetry-Afterheader. - Pick the error family by fault: the caller's fault is a domain error, ours is
PackmindInternalError, a third party's isPackmindUpstreamError. - Put resource ids in the error's
context, never in a message: an upstream error's message reaches the caller, an internal error's never does. - Throw
upstream_unavailable(502, not 503) for an upstream outage, and for any upstream refusal the package does not yet model. - Throw a missing resource and a resource owned by another tenant from a single branch, with one error and one message.
- Use
kind: 'not_found'when a resource belongs to another tenant; reserveforbiddenfor when the caller's own rights are the subject.
Full standard is available here for further request: Domain Error Handling
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 Changed · +6 lines · +230 tokens per session a75feeeba345
- 1mo ago First seen · 15 lines · 273 tokens per session scan A 9abca2f6d162
packmind packmind-domain-error-handling.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 503 tokens to every session, about $0.0020 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-22.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.