Borrowing it
Nothing to install: this file belongs to loong95/javadoc-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/loong95/javadoc-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/loong95/javadoc-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/loong95/javadoc-mcp/agents-md)<a href="https://agentmods.dev/instructions/loong95/javadoc-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/loong95/javadoc-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.00530 | $0.00530 |
| Opus 5 | $0.00265 | $0.00265 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
javadoc-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 8d 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
Source lives under src/. src/index.ts boots the MCP server and registers tools. Tool entrypoints are in src/tools/ (list-packages.ts, get-class.ts, etc.), while JavaDoc fetching and parsing logic lives in src/javadoc/. Shared types are defined in src/types.ts. Build output is generated into dist/; treat that directory as disposable and do not edit it by hand.
Build, Test, and Development Commands
Install dependencies with npm install.
npm run build: compile TypeScript fromsrc/todist/with declarations and source maps.npm start: run the built MCP server fromdist/index.js.npm run dev: run the TypeScript compiler in watch mode during development.npx @modelcontextprotocol/inspector node dist/index.js: inspect the server interactively after a build.
Use Node.js 18+ as noted in the README.
Coding Style & Naming Conventions
Follow the existing TypeScript style in src/: 2-space indentation, semicolons, ES module imports with explicit .js extensions, and strict typing. Prefer small, focused modules and named exports. Keep MCP tool files in kebab-case (get-member.ts) and exported functions in camelCase (getMember). Reuse Zod schemas for tool inputs and keep parsing logic isolated in src/javadoc/.
Testing Guidelines
This checkout does not include an automated test suite yet, and package.json currently defines no test script. For changes that affect parsing or resolution, add focused tests before expanding functionality, and document manual verification steps in the PR. At minimum, verify npm run build succeeds and smoke-test one Maven coordinate through MCP Inspector.
Commit & Pull Request Guidelines
Local Git history is not available in this workspace, so no repository-specific commit convention can be inferred here. Use short, imperative commit subjects such as Add fallback for legacy package lists. Keep commits scoped to one change. PRs should describe the user-visible effect, list verification steps, and note any Maven artifacts or JavaDoc variants used for testing. Include screenshots only when UI tooling output makes review clearer.
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.
- 8d ago First seen · 27 lines · 530 tokens per session scan A 60b8303e3a23
javadoc-mcp AGENTS.md is an instructions file published in the GitHub repository loong95/javadoc-mcp (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 530 tokens to every session, about $0.0027 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.