Borrowing it
Nothing to install: this file belongs to ericyangpan/scan-qrcode-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/ericyangpan/scan-qrcode-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/ericyangpan/scan-qrcode-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/ericyangpan/scan-qrcode-mcp/agents-md)<a href="https://agentmods.dev/instructions/ericyangpan/scan-qrcode-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ericyangpan/scan-qrcode-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.00602 | $0.00602 |
| Opus 5 | $0.00301 | $0.00301 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
scan-qrcode-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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Root: README, LICENSE, and project configs.
src/: Source code for the QR code MCP server (e.g.,src/server.ts,src/routes/,src/services/).tests/: Automated tests mirroringsrc/structure (e.g.,tests/services/qrcode.spec.ts).scripts/: Helper scripts for local dev or CI (optional).assets/: Sample QR images and fixtures for tests/examples (optional).
Example layout:
src/
server.ts
routes/
services/
utils/
tests/
services/
assets/
Build, Test, and Development Commands
npm iorpnpm i: Install dependencies.npm run dev: Start the server in watch mode (TypeScript + nodemon/ts-node).npm run build: Compile TypeScript todist/.npm test: Run unit tests with coverage.npm run lint/npm run format: Lint and format the codebase.
Note: Add these scripts to package.json once the scaffolding is in place.
Coding Style & Naming Conventions
- Language: TypeScript preferred; 2‑space indentation.
- Files: kebab-case (e.g.,
qrcode-service.ts); tests end with.spec.ts. - Naming: camelCase for variables/functions, PascalCase for classes/types, UPPER_SNAKE_CASE for env constants.
- Tools: ESLint (typescript-eslint), Prettier for formatting. Keep imports sorted and paths relative to
src/.
Testing Guidelines
- Framework: Vitest or Jest; aim for ≥80% line coverage on services/utils.
- Structure: Mirror
src/intests/; use fixtures inassets/. - Conventions:
*.spec.ts; one behavior per test, explicit assertions. - Run:
npm testlocally and ensure CI passes before opening a PR.
Commit & Pull Request Guidelines
- Commits: Follow Conventional Commits (e.g.,
feat(server): add health endpoint). - PRs: Include a clear description, linked issues (e.g.,
Closes #12), screenshots or logs when relevant, and notes on breaking changes or migrations. - Scope: Keep PRs small and focused; include tests and update docs.
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.
- 7d ago First seen · 65 lines · 602 tokens per session scan A 9a5a028a3672
scan-qrcode-mcp AGENTS.md is an instructions file published in the GitHub repository ericyangpan/scan-qrcode-mcp (0 stars, last pushed 1y ago), licensed MIT. It adds 602 tokens to every session, about $0.0030 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.