Borrowing it
Nothing to install: this file belongs to yeison-liscano/demo_http_mcp. 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/yeison-liscano/demo_http_mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/yeison-liscano/demo_http_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/yeison-liscano/demo_http_mcp/agents-md)<a href="https://agentmods.dev/instructions/yeison-liscano/demo_http_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/yeison-liscano/demo_http_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.1 | $0.01086 | $0.01086 |
| Opus 5 | $0.00543 | $0.00543 |
| Sonnet 5 | $0.00217 | $0.00217 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
demo_http_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 7d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
Architecture Overview
This is an MCP (Model Context Protocol) server with Auth0 OAuth2 authentication, a chat agent, and a React frontend.
App structure
- Root app (
appinbackend/app/app.py) — Auth0-protected MCP app created byauth_mcp. Handles/mcp/,/register,/.well-known/endpoints. - FastAPI sub-app (
fast_app, mounted at/api) — chat endpoints, frontend serving. Chat endpoints are intentionally unauthenticated for local dev. - Frontend (
frontend/) — React + TypeScript + Vite SPA.
Key modules
| Module | Purpose |
|---|---|
backend/app/app.py |
App setup, routes, MCP + Auth0 wiring |
backend/app/auth0/__init__.py |
Auth0 JWT token validator |
backend/app/auth0/client_store.py |
Dynamic client registration (RFC 7591) |
backend/app/config.py |
pydantic-settings config (Auth0, Logfire) |
backend/app/tools/ |
MCP tools — CPE/CVE search via NVD |
backend/app/agent.py |
pydantic-ai agent streaming logic |
backend/app/agen_memory.py |
SQLite message persistence |
frontend/src/api.ts |
API client (fetch history, stream messages) |
Development Guidelines
Backend
- Python 3.13, managed with
uv - Run from
backend/:uv run run-app(production) oruv run run-app-local(reload) - Lint:
uv run ruff check .— Type check:uv run mypy .— Test:uv run pytest - Follow existing patterns: pydantic models for I/O,
Configfor env vars
Frontend
- React + TypeScript + Vite
- Run from
frontend/:npm run dev(proxies/api/*to backend on 8000) - Lint:
npm run lint— Type check:npx tsc --noEmit
Security rules
- Never log secrets. Use redacted summaries (e.g.
expires_in) not full token responses. - Validate file paths. Any user-controlled path must be
.resolve()d and checked with.is_relative_to()before serving. - CORS: explicit origins only. Never use
allow_origins=["*"]with credentials. - Validate redirect URIs. Only HTTPS allowed; HTTP only for localhost.
- Auth0 env vars go in
backend/.env(git-ignored). Never commit secrets.
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.
- 7d ago First seen · 126 lines · 1,086 tokens per session scan A b01a1af78377
demo_http_mcp AGENTS.md is an instructions file published in the GitHub repository yeison-liscano/demo_http_mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,086 tokens to every session, about $0.0054 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
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).
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.
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).
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.