Borrowing it
Nothing to install: this file belongs to SAP-samples/hana-developer-cli-tool-example. 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/SAP-samples/hana-developer-cli-tool-example/main/.github/instructions/vitepress-config-management.instructions.mdgit clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-exampleWrote 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/sap-samples/hana-developer-cli-tool-example/vitepress-config-management)<a href="https://agentmods.dev/instructions/sap-samples/hana-developer-cli-tool-example/vitepress-config-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/vitepress-config-management/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/sap-samples/hana-developer-cli-tool-example/vitepress-config-management"><img src="https://agentmods.dev/badge/instructions/sap-samples/hana-developer-cli-tool-example/vitepress-config-management.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.03825 | $0.03825 |
| Opus 5.5 | $0.01530 | $0.01530 |
| Sonnet 5.5 | $0.00765 | $0.00765 |
| Haiku 4.5 | $0.00382 | $0.00382 |
Grade B, and why
hana-developer-cli-tool-example vitepress-config-management.instructions.md scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- [ ] Build succeeds without warnings How it starts
The opening of the file, as written. The whole thing — 644 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VitePress Configuration Management Guidelines
Use this guide when creating or modifying VitePress configuration files in the docs/.vitepress/ directory.
Scope and Purpose
This guide applies to VitePress documentation site configuration:
docs/.vitepress/config.ts- Main site configurationdocs/.vitepress/theme/- Custom theme filesdocs/.vitepress/components/- Custom Vue components- Build and deployment configurations
Critical Principles
- Base URL: Always configure correct base URL for GitHub Pages deployment
- Sidebar Structure: Maintain hierarchical, collapsible sidebar navigation
- Mermaid Integration: Use
withMermaid()wrapper for diagram support - Language Alias: Map custom syntaxes to supported highlighters
- SEO Optimization: Include proper meta tags and descriptions
- Clean URLs: Enable clean URLs for better user experience
- Type Safety: Use TypeScript for configuration
Main Configuration Structure
Template: docs/.vitepress/config.ts
import { defineConfig } from 'vitepress'
import { withMermaid } from 'vitepress-plugin-mermaid'
export default withMermaid(
defineConfig({
// Site Metadata
base: '/repository-name/',
title: 'Site Title',
description: 'Site description for SEO',
lang: 'en-US',
// Features
cleanUrls: true,
ignoreDeadLinks: false, // Set true only if needed
appearance: 'dark',
lastUpdated: true,
// Markdown Configuration
markdown: {
languageAlias: {
customLang: 'typescript'
}
},
// HTML Head
head: [
['link', { rel: 'icon', href: '/base-path/favicon.ico' }],
['meta', { name: 'theme-color', content: '#0092d1' }],
['meta', { name: 'og:type', content: 'website' }],
['meta', { name: 'keywords', content: 'keyword1, keyword2' }],
],
// Theme Configuration
themeConfig: {
logo: '/logo.svg',
siteTitle: 'Short Title',
// Navigation
nav: [
// Navigation items
],
// Sidebar
sidebar: {
// Sidebar configuration
},
// Social Links
socialLinks: [
{ icon: 'github', link: 'https://github.com/...' }
],
// Search
search: {
provider: 'local'
},
// Footer
footer: {
message: 'Released under the Apache License.',
copyright: 'Copyright © 2024-present SAP'
}
}
})
)
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 · 644 lines · 3,825 tokens per session scan B 721f99bc77fd
hana-developer-cli-tool-example vitepress-config-management.instructions.md is an instructions file published in the GitHub repository SAP-samples/hana-developer-cli-tool-example (114 stars, last pushed 11d ago), licensed Apache-2.0. It adds 3,825 tokens to every session, about $0.0153 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.