Borrowing it
Nothing to install: this file belongs to shuji-bonji/pdf-spec-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/shuji-bonji/pdf-spec-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/shuji-bonji/pdf-spec-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/shuji-bonji/pdf-spec-mcp/agents-md)<a href="https://agentmods.dev/instructions/shuji-bonji/pdf-spec-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shuji-bonji/pdf-spec-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/shuji-bonji/pdf-spec-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shuji-bonji/pdf-spec-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.01457 | $0.01457 |
| Opus 5.5 | $0.00583 | $0.00583 |
| Sonnet 5.5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
pdf-spec-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 5d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
このリポジトリ（pdf-spec-mcp）で作業するエージェントと人が、最初に読む規則です。開発の手引きは CLAUDE.md、PDF family 全体の計画は pdf-agent-stack の docs/specs/31-openspec-spec-ids-adoption-plan.md にあります。
仕様の正本
- 意図の正本は
openspec/specs/です（OpenSpec の置き場）。Wiki・Discussions・README・docs/NEXT-SESSION.mdは正本にしません。 - 変更は
openspec/changes/<slug>/に出し（openspec new change <slug>）、人が承認するまで実装を始めません。<slug>に日付を入れません（openspec archiveがYYYY-MM-DD-を付けます）。 - 実装する係は
openspec/specs/の本文を直接書き換えません。正本へ取り込むのはopenspec archiveです。実装から仕様へ戻したい発見は、新しいopenspec/changes/に書きます。 openspec/specs/にまだ無いツールは、その変更が触るときに初版を起こします（8 ツールを一斉には起こしません）。初版の下書きは pdf-agent-stack のscripts/openspec-skeleton.mjsでtools/listから出せます（引数の表だけ。振る舞いの要求は既存のテストから起こします）。
仕様 ID
- 形式は
SPEC-PDFSPEC-<機能>-<3 桁>です（例:SPEC-PDFSPEC-GET-REQUIREMENTS-001）。機能はopenspec/specs/<capability>/spec.mdのディレクトリ名を大文字にしたものです（capability はツール名の_を-にした kebab-case）。番号は機能ごとに 001 からの通し番号です。 - 要求の見出しは
### Requirement: SPEC-PDFSPEC-<機能>-<3 桁> 題の形で書きます。各要求に#### Scenario:を 1 つ以上書き、Scenario 名をテスト名の後半にします。 - 新しい ID は
npx spec-ids next <capability>で取ります（複数なら--count 3）。一度使った番号はその機能の中で再利用しません。 - 仕様を外すときは差分の
## REMOVED Requirementsに書き、テストからも ID を外します。
テストの置き場
src/**/*.test.ts（単体テスト）は CI で回ります。tests/e2e/**/*.test.tsは仕様 PDF（PDF_SPEC_DIR）が要るので、仕様 PDF のある手元でしか回りません。spec-ids checkは両方のテスト名を読みます。CI で確かめたい要求の受入テストはsrc/側に置きます。
承認の記録
openspec/changes/<slug>/proposal.mdの先頭の front matter にapproved: YYYY-MM-DD（JST）とpr: Nを人が書きます。エージェントは空のキー（approved:・pr:）のまま出します。implementation（required/none）とtargets（書き換える capability の配列）はエージェントが書きます。openspec/specs/<capability>/spec.mdの front matter にはspec_id: PDFSPEC・kind（tool/common）・introduced_by（その capability を作った変更の slug）を書きます。- 🔴 新しい capability を作る変更では、
openspec archiveが差分の front matter を正本に写しません（OpenSpec 1.14.1）。archive の後、正本の先頭に front matter を書き足してからnpx spec-ids checkを回します。
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.
- 5d ago First seen · 46 lines · 1,457 tokens per session scan A 1f075533d9fd
pdf-spec-mcp AGENTS.md is an instructions file published in the GitHub repository shuji-bonji/pdf-spec-mcp (2 stars, last pushed 3d ago), licensed MIT. It adds 1,457 tokens to every session, about $0.0058 per session on Opus 5.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-10-23.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.