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/agutschow/2026developerdays/claude-mdgit clone --depth 1 https://github.com/agutschow/2026DeveloperDaysWrote 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/agutschow/2026developerdays/claude-md)<a href="https://agentmods.dev/instructions/agutschow/2026developerdays/claude-md"><img src="https://agentmods.dev/badge/instructions/agutschow/2026developerdays/claude-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 | $0.01316 | $0.01316 |
| Opus 5 | $0.00658 | $0.00658 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
2026DeveloperDays 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 4d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SailPoint ISC Development Context
What We're Building
Integrations against SailPoint Identity Security Cloud (ISC) using the REST API and Python SDK. These are scripts and automations — not web applications.
Project Structure
api-specs/— cloned from https://github.com/sailpoint-oss/api-specs — rungit pullto stay currentsrc/— Python scripts for each scenariodocs/isc-development-guide.md— ISC development patterns and reference (read this for domain context)docs/getting-started.md— human setup guide
API Version Selection
SailPoint ISC has versioned APIs. Each version is supported for 3 years from its release year (e.g., v2026 is supported through 2029).
When asked about a specific endpoint or operation, read the relevant YAML files in api-specs/idn/ before answering. Do not rely on training data for endpoint details — the specs are ground truth.
When identifying which API call to use:
- Check what version folders exist in
api-specs/idn/— this reflects what is currently available - Start with the highest version folder present
- Search for the endpoint there first
- If the endpoint is not in the highest version, fall back to the next lower version and repeat
- Avoid v3 — support ends Q1 2027, no new functionality
- The version whose spec contains the endpoint is the version to import from in code
On beta: The beta folder in api-specs is legacy. New experimental features appear in versioned
APIs with an experimental flag — not in a separate beta branch.
On /latest: SailPoint introduced a /latest version alias in February 2026 that automatically
routes to the current annual version (https://{tenant}.api.identitynow.com/latest/{endpoint}).
- One-time or bulk scripts: use
/latestunconditionally. - Ongoing integrations:
/latestis the right default. Treat each SailPoint annual release as a change event — review release notes and test the integration when a new version ships. - Explicit versioning: appropriate only when there is a specific reason to pin (regulatory requirement, change-freeze environment). Pinning to an explicit version defers the same maintenance problem to a 3-year end-of-life cliff, it does not eliminate it.
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.
- 4d ago First seen · 145 lines · 1,316 tokens per session scan A 51333d5147a6
2026DeveloperDays CLAUDE.md is an instructions file published in the GitHub repository agutschow/2026DeveloperDays (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0066 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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.