Borrowing it
Nothing to install: this file belongs to YZDame/geogebra-mcp-server. 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/YZDame/geogebra-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/YZDame/geogebra-mcp-serverWrote 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/yzdame/geogebra-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/yzdame/geogebra-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/yzdame/geogebra-mcp-server/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.00438 | $0.00438 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
geogebra-mcp-server 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 6d 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
Project Context
- Project type: Node.js + TypeScript MCP server for GeoGebra.
- Runtime role: this repo is an MCP tool server (not a chat UI).
- Main flow: client LLM -> MCP JSON-RPC -> tool registry -> GeoGebra execution -> structured response/export.
Code Map
- Entry:
src/index.ts, CLI:src/cli.ts - MCP server:
src/server.ts - Tool registration:
src/tools/index.ts - Core GeoGebra tools:
src/tools/geogebra-tools.ts - Educational templates:
src/tools/educational-templates.ts - Performance tools:
src/tools/performance-tools.ts - GeoGebra engine wrapper:
src/utils/geogebra-instance.ts - Validation and errors:
src/utils/validation.ts,src/utils/errors.ts - Tests:
tests/unit,tests/e2e,tests/performance
Development Rules
- Treat
src/as source of truth.dist/is build output. - Keep MCP stdout clean: do not print non-JSON content in request/response flow.
- Keep tool schemas explicit (
typefor properties) to stay Gemini-compatible. - Preserve backward compatibility for existing tool names and response shapes unless explicitly requested.
- For file outputs, keep workspace path validation (no path traversal).
Tool Implementation Checklist
When adding/updating a tool:
- Define clear
inputSchemainToolDefinition. - Validate inputs with
src/utils/validation.ts(or add focused validators). - Use consistent success/error payload format (
content+isErrorwhen needed). - Handle GeoGebra failures with actionable error text.
- Add/adjust tests in
tests/unitand integration/e2e tests when behavior changes.
Local Commands
- Install:
npm install - Build:
npm run build - Dev run:
npm run dev - CLI run:
node dist/cli.js - Test:
npm test - Coverage:
npm run test:coverage
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.
- 6d ago First seen · 47 lines · 438 tokens per session scan A 2c7828b2cd94
geogebra-mcp-server AGENTS.md is an instructions file published in the GitHub repository YZDame/geogebra-mcp-server (2 stars, last pushed 6mo ago), licensed MIT. It adds 438 tokens to every session, about $0.0022 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.