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.
npx agentmods add instructions/radu103/github-copilot-vscode-sap-dev-instructions/1-sap-capgit clone --depth 1 https://github.com/radu103/github-copilot-vscode-sap-dev-instructionsWrote 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/radu103/github-copilot-vscode-sap-dev-instructions/1-sap-cap)<a href="https://agentmods.dev/instructions/radu103/github-copilot-vscode-sap-dev-instructions/1-sap-cap"><img src="https://agentmods.dev/badge/instructions/radu103/github-copilot-vscode-sap-dev-instructions/1-sap-cap.svg" alt="Measured on agentmods" 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 | $0.00528 | $0.00528 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
github-copilot-vscode-sap-dev-instructions 1-sap-cap.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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Programming language and tools
- SAP CAP Framework documentation
- Docs for services: https://cap.cloud.sap/docs/node.js/
- Docs for SAP CAP CDS: https://cap.cloud.sap/docs/cds/cdl
- Docs for SAP CAP: https://cap.cloud.sap/docs/guides/
- JavaScript implementation for services and the UI5 freestyle app
- UI5 XML views only
- ESLint validation and fixes
- Enforce and obey rules in the .github folder; ask for permission otherwise.
- Use Husky to run lint:fix on committed files.
- Never use Python to solve anything; use JavaScript/Node.js tools.
Naming conventions
- Always use camelCase for all names of variables and properties.
- Use capitalized names for services and entities.
- For variable declaration use
letinstead ofvar
Database model rules
- Do not use UUID; use String(36) instead. No deterministic ids and no UIID-MAPPING but always consistent references.
- All entities use the cuid aspect.
- All entities use the managed aspect.
- All entity names are always as singular, never plural in db and services.
- Generated CSV data must not import managed fields :
createdAt,createdBy,modifiedAt,modifiedBy - Associations are defined using two fields: referenceID of type String(36) and the association on that reference field.
- Do not use compositions. No
Composition oforcomposition ofusage. - All types are in the types.cds file and are reused.
- Entities are in separate files based on the main relationship domain.
- Use Integer enums with text names.
- Use an isActive boolean property and always use soft-delete logic; only hard-delete from persisted data in case of user roles.
- Data IDs marked as cuid always generate UUID v4 strings for data/migration and testing purposes, but the database model uses String(36) to store them.
Backend rules
- Reuse all entities and types from the db/* folder.
- All services are in the srv folder.
- All services include model associations.
- Do not use compositions.
- No UI annotations in srv/* services.
- All services are annotated with "@requires: 'authenticated-user'".
- Never use @odata.draft.enabled.
- CAP service actions and functions that return complex types must use types created in db/types.cds and reused with using.
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.
- 4d ago First seen · 53 lines · 528 tokens per session scan A 1ee753b66e57
github-copilot-vscode-sap-dev-instructions 1-sap-cap.instructions.md is an instructions file published in the GitHub repository radu103/github-copilot-vscode-sap-dev-instructions (8 stars, last pushed 3mo ago), licensed MIT. It adds 528 tokens to every session, about $0.0026 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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.