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/narumiruna/ly-mcp/agents-mdgit clone --depth 1 https://github.com/narumiruna/ly-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/narumiruna/ly-mcp/agents-md)<a href="https://agentmods.dev/instructions/narumiruna/ly-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/narumiruna/ly-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.00748 | $0.00748 |
| Opus 5 | $0.00374 | $0.00374 |
| Sonnet 5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
ly-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 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/lymcp/api.pycontains request models and HTTP calls tohttps://ly.govapi.tw/v2.src/lymcp/server.pyregisters FastMCP tools, prompts, and resources.src/lymcp/translate.pymaps internal parameter names to upstream Chinese query fields.tests/test_api_mock.pyandtests/test_server_mock.pyare default offline tests.tests/test_api.pyandtests/test_server.pyare live tests marked@pytest.mark.live.tests/data/stores checked-in JSON fixtures for deterministic tests.docs/contains endpoint audits and archived implementation plans.
Swagger Contract Alignment
- Treat the repository-root
swagger.yaml, refreshed from the upstream API withscripts/download-swagger.sh, as the source of truth for supported endpoints and query parameters. - When
swagger.yamlchanges, implement every documented endpoint and query parameter end to end across request models insrc/lymcp/api.py, MCP tools insrc/lymcp/tools/, CLI commands insrc/lymcp/commands/, and agent guidance inskills/ly/SKILL.md. - Keep
tests/test_swagger_coverage.pyand the relevant API, MCP, CLI, live, README, and endpoint-audit coverage synchronized; verify contract-alignment changes withjust lint,just type, andjust test.
Build, Test, and Development Commands
uv syncinstalls project and development dependencies.just lintruns Ruff checks.just typerunstytype checking.just testruns the offline pytest suite with coverage.just test-liveruns live tests against the Legislative Yuan API.just devstarts the MCP Inspector forsrc/lymcp/server.py.uv run lymcpruns the MCP server locally.
Coding Style & Naming Conventions
Write Python with 4-space indentation and type annotations for public or shared code. Name request classes by action and endpoint, for example ListBillRequest or GetLawVersionRequest. Keep MCP tool functions snake_case and aligned with endpoint intent, for example list_bills.
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 · 50 lines · 748 tokens per session scan A ec3b06620a4f
ly-mcp AGENTS.md is an instructions file published in the GitHub repository narumiruna/ly-mcp (6 stars, last pushed 5d ago), licensed MIT. It adds 748 tokens to every session, about $0.0037 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.
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 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.