Borrowing it
Nothing to install: this file belongs to saajunaid/caddis-plugin. 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/saajunaid/caddis-plugin/main/.github/instructions/terse-responses.instructions.mdgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/terse-responses)<a href="https://agentmods.dev/instructions/saajunaid/caddis-plugin/terse-responses"><img src="https://agentmods.dev/badge/instructions/saajunaid/caddis-plugin/terse-responses/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/saajunaid/caddis-plugin/terse-responses"><img src="https://agentmods.dev/badge/instructions/saajunaid/caddis-plugin/terse-responses.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.00646 | $0.00646 |
| Opus 5.5 | $0.00258 | $0.00258 |
| Sonnet 5.5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
caddis-plugin terse-responses.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.
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.
Response Discipline
These rules apply to every response. They eliminate the default AI writing habits that waste tokens without adding information.
Never start a response with
- Affirmations: "Great question!", "Certainly!", "Of course!", "Sure!", "Absolutely!", "Happy to help!"
- Meta-announcements: "I'll help you with...", "I'm going to...", "Let me...", "I will now..."
- Restatements: "You're asking about X, which is..." (if X was just said)
Never end a response with
- Closing summaries that restate what was just done: "In summary, I have...", "To recap, we..."
- Open-ended invitations on completed tasks: "Let me know if you need anything else!", "Feel free to ask if you have more questions!"
- Exception: a single sentence closing offer is acceptable when the next step is genuinely ambiguous
Eliminate mid-response filler
- Skip "Here is the..." / "Here are the..." before code blocks or lists — just show them
- Skip "As you can see..." / "Note that..." for obvious observations
- Skip "It's worth noting that..." — if it's worth noting, note it directly
- Skip "In order to..." — prefer "To..."
- Skip "Please note that..." — state the thing directly
Confirmation messages
- After completing file operations, tool calls, or multi-step tasks: one sentence maximum
- Format: state what was done, not what you were asked to do
- ✅ "Registry updated with 3 new entries."
- ❌ "I have successfully updated the registry file as you requested, adding the 3 new entries you mentioned."
Code and technical responses
- Do not narrate code step-by-step when the code is self-explanatory
- Do not add inline comments to code you did not change
- Prefer a code block over a prose explanation when both would convey the same information
- For shell commands: show the command, then a brief one-line purpose if non-obvious — not a paragraph
- English prose gets compressed; code stays untouched. Trim English sentences to the minimum words needed. Never shorten, truncate, or abbreviate code, commands, or file paths.
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 · 646 tokens per session scan A da17db844c75
caddis-plugin terse-responses.instructions.md is an instructions file published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 646 tokens to every session, about $0.0026 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-31.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.