Borrowing it
Nothing to install: this file belongs to JunctionX-Korea-2026-JoyRide/gyeongbuk-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/JunctionX-Korea-2026-JoyRide/gyeongbuk-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/JunctionX-Korea-2026-JoyRide/gyeongbuk-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/junctionx-korea-2026-joyride/gyeongbuk-mcp/agents-md)<a href="https://agentmods.dev/instructions/junctionx-korea-2026-joyride/gyeongbuk-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/junctionx-korea-2026-joyride/gyeongbuk-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/junctionx-korea-2026-joyride/gyeongbuk-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/junctionx-korea-2026-joyride/gyeongbuk-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00555 | $0.00555 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
gyeongbuk-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 11d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project overview
This repository contains an MCP (Model Context Protocol) server that exposes location and public-data capabilities as tools for AI agents.
Keep the project focused on the MCP server. Do not add a frontend, chat UI, or standalone agent unless explicitly requested.
Project structure
src/
├── server.py # MCP server entry point
├── tools/ # MCP tool definitions
├── services/ # Business logic
├── clients/ # External API clients
└── models/ # Input/output models
tests/
Keep MCP tool definitions thin. Put API access in clients/ and reusable logic in services/.
Development
- Use Python 3.12+.
- Use FastMCP for the MCP server.
- Use
uvfor dependency and environment management. - Use type hints for all public functions.
- Prefer async I/O for external API calls.
- Keep dependencies minimal.
Setup and validation commands
- Install dependencies:
uv sync - Run the server:
make run - Type-check:
make typecheck - Format:
make format - Check formatting:
make format-check - Lint:
make lint - Test:
make test - Run all non-mutating checks:
make check - Install pre-commit hooks:
make hooks
MCP tool guidelines
- Each tool should have one clear responsibility.
- Use descriptive tool names and concise docstrings.
- Use typed inputs and structured outputs.
- Return facts and metadata rather than LLM-generated reasoning.
- Keep outputs deterministic when possible.
- Handle missing data and external API failures explicitly.
- Do not expose secrets or internal exception details.
Example tools may include:
search_nearby_facilitiesget_public_transport_accessget_safety_dataget_location_metricscompare_locations
Testing
- Add tests for new tools and business logic.
- Mock external APIs in unit tests.
- Test invalid inputs, missing data, timeouts, and API failures.
- Run the full test suite before finishing a change.
Security
- Never hardcode API keys or credentials.
- Read secrets from environment variables.
- Validate external inputs.
- Set timeouts on external HTTP requests.
- Do not log sensitive credentials.
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.
- 11d ago First seen · 88 lines · 555 tokens per session scan A 83d27379dd38
gyeongbuk-mcp AGENTS.md is an instructions file published in the GitHub repository JunctionX-Korea-2026-JoyRide/gyeongbuk-mcp (0 stars, last pushed 6d ago), licensed MIT. It adds 555 tokens to every session, about $0.0028 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
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.
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).
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).