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/hellowda253/kit-pucp-mcp/agents-mdgit clone --depth 1 https://github.com/Hellowda253/KIT-PUCP-MCPWrote 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/hellowda253/kit-pucp-mcp/agents-md)<a href="https://agentmods.dev/instructions/hellowda253/kit-pucp-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hellowda253/kit-pucp-mcp/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 | $0.00794 | $0.00794 |
| Opus 5 | $0.00397 | $0.00397 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
KIT-PUCP-MCP 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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instalación de PUCP-MCP por agentes
Estas instrucciones se aplican cuando un usuario pide instalar o actualizar este
repositorio desde un enlace. El alcance inicial es Codex, Antigravity, Claude Code
y Claude Desktop en Windows; para otro cliente, usa su formato MCP stdio vigente.
Secuencia obligatoria
- Identifica el cliente, el sistema y si la instalación será de usuario o proyecto.
- Clona la etiqueta estable más reciente en una ubicación persistente. Si el repositorio aún no tiene etiquetas, usa la rama predeterminada e informa esa limitación. No ejecutes el MCP desde una carpeta temporal.
- Comprueba Node.js 20 o posterior y ejecuta
npm cien la raíz. - Si falta
.env.local, créalo a partir de.env.example. - Configura credenciales según la sección siguiente.
- Ofrece una sola vez configurar una biblioteca académica. El usuario puede elegir
una carpeta existente o autorizar la creación de una nueva; si acepta, guarda su
ruta absoluta en
PUCP_DOWNLOADS_DIR. No crees carpetas sin permiso ni insistas si prefiere conservar el destino predeterminado. - Ejecuta
npm run install-config -- --client CLIENTE --root RUTA_ABSOLUTA. - Lee la configuración vigente del cliente y crea una copia de seguridad antes de
cambiarla. Conserva todos los servidores ajenos y combina únicamente
paideia,campus_virtual_pucpypucp_academic_overview. - Instala las carpetas completas de
skills/de forma recursiva, incluidosassets/,references/,scripts/yagents/, con el mecanismo admitido por el cliente. No sustituyas silenciosamente una versión más nueva. - Ejecuta
npm run doctor -- --json; después verificainitializeytools/listdesde el cliente. - Informa archivos modificados, pruebas realizadas y reversión disponible sin mostrar secretos.
Credenciales proporcionadas en el chat
El usuario puede entregar voluntariamente sus credenciales PUCP en el chat y pedir que el agente las use o guarde. Esa autorización se limita a esta instalación.
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 · 59 lines · 794 tokens per session scan A 78a610cbf664
KIT-PUCP-MCP AGENTS.md is an instructions file published in the GitHub repository Hellowda253/KIT-PUCP-MCP (3 stars, last pushed today), licensed MIT. It adds 794 tokens to every session, about $0.0040 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.