Borrowing it
Nothing to install: this file belongs to santiagosanmartinn/mcpui5server. 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/santiagosanmartinn/mcpui5server/main/AGENTS.mdgit clone --depth 1 https://github.com/santiagosanmartinn/mcpui5serverWrote 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/santiagosanmartinn/mcpui5server/agents-md)<a href="https://agentmods.dev/instructions/santiagosanmartinn/mcpui5server/agents-md"><img src="https://agentmods.dev/badge/instructions/santiagosanmartinn/mcpui5server/agents-md.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.1 | $0.00497 | $0.00497 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
mcpui5server AGENTS.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 5d 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.
What it actually says
AGENTS.md
Instrucciones de trabajo para asistentes de IA (Codex/otros) en este repositorio.
Objetivo
Usar el servidor MCP SAPUI5 como capa principal de analisis y generacion para maximizar:
- calidad tecnica,
- trazabilidad de cambios,
- seguridad en ediciones.
Regla principal: MCP-first
Antes de editar codigo, usar tools MCP para entender contexto y preparar cambios.
Flujo minimo recomendado por tarea:
analyze_ui5_projectsearch_project_filesy/oanalyze_current_file- Tool especifica del dominio:
- UI5:
generate_ui5_*,validate_ui5_code,manage_ui5_i18n,analyze_ui5_performance - JS:
refactor_javascript_code,lint_javascript_code,security_check_javascript - Proyecto:
sync_manifest_json(si aplica)
- UI5:
- Si hay escritura de archivos, usar primero
write_project_file_preview - Aplicar cambios con
apply_project_patch - Ejecutar
npm run check - Si algo falla o hay regresion, usar
rollback_project_patch
Politica de cambios
- Preferir
dryRun: trueen tools que modifican (generate_ui5_feature,manage_ui5_i18n,sync_manifest_json) para revisar antes de aplicar. - Evitar ediciones manuales directas de
manifest.jsoncuando el cambio encaje ensync_manifest_json. - Mantener cambios pequenos y verificables.
Politica de validacion
Tras cada cambio relevante:
- Validar codigo UI5 con
validate_ui5_codeen archivos nuevos/modificados. - Ejecutar
analyze_ui5_performancesobre el modulo afectado. - Ejecutar
manage_ui5_i18nen modoreport(ofixcondryRun) si se tocaron vistas XML/literales. - Ejecutar
npm run checkcomo puerta final de calidad.
Documentacion y referencias
- Arquitectura:
docs/arquitectura-interna.md - Referencia tools:
docs/referencia-tools.md - Ejemplos de uso:
docs/ejemplos-tools.md - Integracion con Codex:
docs/integracion-codex-vscode.md
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.
- 5d ago First seen · 51 lines · 497 tokens per session scan A 5ee68105f011
mcpui5server AGENTS.md is an instructions file published in the GitHub repository santiagosanmartinn/mcpui5server (0 stars, last pushed 3mo ago), licensed MIT. It adds 497 tokens to every session, about $0.0025 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
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.
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.
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).
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).
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.
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.