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/oisee/vibing-steampunk/copilot-instructionsgit clone --depth 1 https://github.com/oisee/vibing-steampunkWhat 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.01439 | $0.01439 |
| Opus 5 | $0.00720 | $0.00720 |
| Sonnet 5 | $0.00288 | $0.00288 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
vibing-steampunk 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- MCP_SAP copilot-instructions.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for vsp
Project
vsp is a Go-native MCP (Model Context Protocol) server that bridges AI agents to SAP ABAP systems via the ADT REST API. Single binary, 9 platforms, zero dependencies. It exposes 81 tools (focused mode) or 122 tools (expert mode) over JSON-RPC/stdio.
Build, Test, Lint
# Build
go build -o vsp ./cmd/vsp
# Run all unit tests
go test ./...
# Run a single test by name
go test -run TestSafetyReadOnly -v ./pkg/adt/
# Run a single package's tests
go test -v ./pkg/cache/
# Integration tests (require live SAP system via SAP_* env vars)
go test -tags=integration -v ./pkg/adt/
# Lint (golangci-lint with .golangci.yml config)
golangci-lint run ./...
# Format (gofumpt preferred, falls back to go fmt)
gofumpt -w .
Architecture
cmd/vsp/main.go → CLI entry point (cobra + viper)
internal/mcp/
server.go → MCP server struct, initialization
tools_register.go → Tool registration logic (mode + group filtering)
tools_focused.go → Focused-mode tool whitelist
tools_groups.go → Disableable tool groups (5/U, T, H, D, C, G, R, I, X)
handlers_*.go → One file per tool category (20+ handler files)
pkg/adt/
config.go → ADT client config (functional options pattern)
client.go → Main client facade + read operations
http.go → HTTP transport (CSRF token refresh, session management)
crud.go → Lock → Update → Unlock → Activate lifecycle
workflows.go → High-level composite operations (GetSource, WriteSource)
workflows_edit.go → EditSource (find-replace with syntax check)
safety.go → Operation filtering and package restrictions
features.go → Runtime feature probing (auto/on/off)
debugger.go → External ABAP debugger (WebSocket via ZADT_VSP)
xml.go → XML type definitions for ADT responses
pkg/dsl/ → Fluent API for search, test, batch, YAML workflows
pkg/cache/ → In-memory + SQLite caching
pkg/scripting/ → Lua scripting engine (40+ ADT bindings)
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.
- 3d ago First seen · 118 lines · 1,439 tokens per session scan A f566282d15ad
vibing-steampunk copilot-instructions.md is an instructions file published in the GitHub repository oisee/vibing-steampunk (448 stars, last pushed 6d ago), licensed MIT. It adds 1,439 tokens to every session, about $0.0072 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-30.
Other instructions, from other repositories
mcp-abap-adt CLAUDE.md
Instructions for fr0ster/mcp-abap-adt, covering mcp abap adt - development guide, testing, integration tests, soft mode (mass run) — save full log and test configuration.
aibap.mcp CLAUDE.md
Instructions for Hochfrequenz/aibap.mcp, covering claude.md, project overview, build & run, testing and workflow.
dassian-adt CLAUDE.md
Instructions for DassianInc/dassian-adt, covering claude.md, commands, architecture, request flow and handler hierarchy.
sap-adt-mcp CLAUDE.md
Claude Code instructions for engoetz/sap-adt-mcp, covering claude.md, what this is, commands, architecture and invariants that are easy to break.
sap-adt-mcp AGENTS.md
AGENTS.md instructions for engoetz/sap-adt-mcp, covering sap adt python — agent instructions, available mcp tools, abap development workflow, first-time setup (once per environment) and before editing any abap object.
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.