Borrowing it
Nothing to install: this file belongs to jackvaughanjr/jamf-platform-mcp-server. 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/jackvaughanjr/jamf-platform-mcp-server/main/CLAUDE.mdgit clone --depth 1 https://github.com/jackvaughanjr/jamf-platform-mcp-serverWrote 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/jackvaughanjr/jamf-platform-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/jackvaughanjr/jamf-platform-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/jackvaughanjr/jamf-platform-mcp-server/claude-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/jackvaughanjr/jamf-platform-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/jackvaughanjr/jamf-platform-mcp-server/claude-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.01179 | $0.01179 |
| Opus 5 | $0.00589 | $0.00589 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
jamf-platform-mcp-server CLAUDE.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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repo
Rules for working here. Two companion documents carry what this one deliberately does not:
docs/gateway-reference.md— what the Jamf Platform API Gateway actually does: path shapes, confirmed routes, status semantics, pagination. Findings about a beta product; expect them to change.decisions/— why the project is built this way. Immutable.
Never force-add ignored files
git add -f / git add --force is not permitted in this repo, and neither is
git update-index --add on an ignored path. A .githooks/pre-commit hook rejects
any staged file that .gitignore covers, so a force-add fails at commit time
rather than silently landing.
The ignore list is a data-handling boundary, not tidiness. It guards:
- the OAuth client secret (
.env) — shown exactly once at integration creation - raw gateway responses (
fixtures/raw/,blueprints.json) containing live device serials, usernames, email addresses, IPs, and per-device application inventory
If something currently ignored genuinely belongs in version control, change
.gitignore in its own commit so the decision is reviewable. Rationale:
JPM-0004.
Committed ADRs are immutable
scripts/check-adr-immutability.sh blocks modifying, deleting, or renaming an ADR
that is already committed. Corrections go by a new superseding record. Before a
record has external readers, an in-place edit is available via
ADR_ALLOW_EDIT=1 git commit. See decisions/README.md.
Credentials
Never write the client secret to disk. Credentials live in 1Password; inject them at runtime:
cp .env.op.example .env.op # then edit to match your vault/item
op run --env-file=.env.op -- ./scripts/discover-gateway.sh
Only .env.op.example is tracked. A real .env.op holds no secrets — just
op:// references — but those references name a local 1Password vault and item,
which is org-internal detail that does not belong in a repo shared outside the
company. Keep it untracked.
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 · 96 lines · 1,179 tokens per session scan A dc9126fe38dd
jamf-platform-mcp-server CLAUDE.md is an instructions file published in the GitHub repository jackvaughanjr/jamf-platform-mcp-server (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,179 tokens to every session, about $0.0059 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.