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/fridaruh/mcp_tools4foresight/agents-mdgit clone --depth 1 https://github.com/fridaruh/MCP_Tools4ForesightWrote 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/fridaruh/mcp_tools4foresight/agents-md)<a href="https://agentmods.dev/instructions/fridaruh/mcp_tools4foresight/agents-md"><img src="https://agentmods.dev/badge/instructions/fridaruh/mcp_tools4foresight/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.00523 | $0.00523 |
| Opus 5 | $0.00262 | $0.00262 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
MCP_Tools4Foresight 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 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.
What it actually says
Reglas para agentes que trabajen en este repo
Este es el servidor MCP de solo lectura de tools4foresight. Antes de tocar nada,
lee docs/ARCHITECTURE.md y docs/API.md.
Invariantes
- Es de SOLO LECTURA y para EXPLORAR. Nunca agregues una tool, un resource o un método de cliente que escriba, modifique o borre algo. Nada de operaciones de administración (publicar, editar análisis, recalcular el grafo): eso vive en tools4foresight. Si una tarea parece pedirlo, pregunta antes. Los prompts son guiones de conversación y no dan capacidades: si agregas uno, que solo encadene tools de lectura.
stdoutes el canal JSON-RPC en stdio. Todo log va astderr. Unconsole.logrompe el protocolo.- No inventes campos. El contrato es
docs/API.md. Si un campo no está ahí, la API no lo devuelve, por muy razonable que suene. - Cero dependencias nuevas sin una razón explícita: solo
@modelcontextprotocol/sdkyzod. - Imports internos con extensión
.js(moduleResolution: NodeNext). - Toda tool nueva necesita test y una sección en
docs/TOOLS.md.
Vocabulario del dominio (no lo traiciones)
- Una señal es contenido curado guardado como indicio de futuro.
- Un tema es un linaje que persiste entre corridas; puede morir y resucitar. Un tema muerto es un fósil, no un borrado: se dice "fósil", nunca "eliminado".
likedAtes una estimación: se muestra siempre con~.- El porcentaje de similitud no se le muestra a una persona: se usa
strength(fuerte/media/débil). Elscorees para el razonamiento del agente. - Los ids de macro-tema no son estables entre corridas.
El glosario completo vive en src/domain/glossary.ts y se rinde en
docs/DOMAIN.md. Es la fuente única: no dupliques definiciones.
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 · 36 lines · 523 tokens per session scan A 34ffccae4b3b
MCP_Tools4Foresight AGENTS.md is an instructions file published in the GitHub repository fridaruh/MCP_Tools4Foresight (0 stars, last pushed 9d ago), licensed MIT. It adds 523 tokens to every session, about $0.0026 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.