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/apps/cli/.github/instructions/packmind-cli-packmindgateway-method-implementation.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-cli-packmindgateway-method-implementation)<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-cli-packmindgateway-method-implementation"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-cli-packmindgateway-method-implementation/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-cli-packmindgateway-method-implementation"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-cli-packmindgateway-method-implementation.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.00267 | $0.00267 |
| Opus 5.5 | $0.00107 | $0.00107 |
| Sonnet 5.5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
packmind packmind-cli-packmindgateway-method-implementation.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: CLI Gateway Implementation
When adding new methods to the PackmindGateway class in the CLI application, use the PackmindHttpClient abstraction to avoid code duplication and maintain consistency. The older methods contain extens... :
- Define the method return type using
Promise<ResponseType>for type safety - Gateway implementations methods should always be typed using
Gateway<UseCase> - Gateway interfaces should only expose
Gateway<UseCase> - Gateway should never expose custom command or response types
- Keep gateway methods concise by delegating authentication and error handling to
PackmindHttpClient - PackmindGateway must delegate to sub-gateways for each hexa
- Pass HTTP method and body via options object to
httpClient.request()for non-GET requests (e.g.,{ method: 'POST', body: data }) - Use
this.httpClient.getAuthContext()to retrieveorganizationIdinstead of manually decoding the API key and JWT - Use
this.httpClient.request<ResponseType>()for all HTTP calls instead of manual fetch with duplicated error handling
Full standard is available here for further request: CLI Gateway Implementation
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 · 17 lines · 267 tokens per session scan A 0d1c297c7372
packmind packmind-cli-packmindgateway-method-implementation.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 267 tokens to every session, about $0.0011 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 instructions, from other repositories
plan-forge api-patterns.instructions.md
API patterns for .NET — REST conventions, ProblemDetails, pagination, versioning, error responses.
plan-forge messaging.instructions.md
Messaging patterns for .NET — Dapr Pub/Sub, MassTransit, NATS, RabbitMQ, CloudEvents.
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.