deep-init copilot-instructions.md

Repository instructions for deep-init that give coding agents context about Kemal, a Sinatra-style web framework for the Crystal programming language. They describe its middleware pipeline, global DSL, project components and reference documentation.

In plain words
What is it for?
Use them when working on the Kemal codebase, especially its request handlers, configuration, lifecycle, DSL or related components.
Why use it?
They reduce the need to rediscover the framework’s architecture and important project rules before changing code.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/deepfusionlabs/deep-init/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/deepfusionlabs/deep-init

Made for: GitHub Copilot.

Per session 1,688 This file is loaded in full into every session.
When invoked 1,688 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01688 $0.01688
Opus 5 $0.00844 $0.00844
Sonnet 5 $0.00338 $0.00338
Haiku 4.5 $0.00169 $0.00169

Measured 2d ago against content hash 4e22fc25d973, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deep-init copilot-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 2d 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.

validation/end-to-end/kemal/.github/copilot-instructions.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository instructions (Copilot projection)

Canonical context lives in AGENTS.md + .ai/docs/ — this file is a generated projection of the lean tier; do not edit inside the DeepInit markers (regenerated each run).

kemal — Agent Context

Kemal is a lean, Sinatra-style HTTP web framework for the Crystal language: a global-scope DSL (get "/" {... }, ws, sse, before_all, use, mount) layered over a fixed HTTP::Handler middleware chain that a single process-wide Config singleton assembles and owns.

Architecture

A composable HTTP::Handler middleware pipeline driven by a Sinatra-style global DSL over a process-global Config singleton. The whole src/kemal/ tree is loaded by three glob requires in src/kemal.cr; files reference siblings by fully-qualified constants, not per-file imports. Components map to .ai/docs/components/.

Components (7)

  • core — entry point + global run/stop lifecycle + the Config singleton that assembles the ordered handler chain + the top-level DSL + CLI/SSL. → .ai/docs/components/core.md
  • handlers — the HTTP::Handler middleware links (init, exception, head, override-method, path, static-file, filter) + the base handler with only/exclude matching. → .ai/docs/components/handlers.md
  • router — route storage/matching/dispatch: the terminal RouteHandler + LRU route cache, the modular Router DSL, and param parsing with body-size guards. → .ai/docs/components/router.md
  • websocket — real-time transports: WebSocketHandler (Origin allow-list), the WS route wrapper, and Server-Sent Events. → .ai/docs/components/websocket.md
  • helpers — global view/response helpers, ECR templating macros, the exception hierarchy, and path/zip utilities. → .ai/docs/components/helpers.md
  • logging — pluggable request-logging abstraction (deprecated in favor of stdlib Log); the default RequestLogHandler + legacy/no-op loggers. → .ai/docs/components/logging.md
  • ext — stdlib monkey-patches (NOT under Kemal::): reopens HTTP::Server::Context (params/redirect/route lookup + typed @store) and HTTP::Server::Response. → .ai/docs/components/ext.md

Read the full file on GitHub · 50 lines

Changes

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.

  1. 2d ago First seen · 50 lines · 1,688 tokens per session scan A 4e22fc25d973

Subscribe to this mod's changes

deep-init copilot-instructions.md is an instructions file published in the GitHub repository deepfusionlabs/deep-init (6 stars, last pushed 13d ago), licensed MIT. It adds 1,688 tokens to every session, about $0.0084 per session on Opus 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-31.