What is 2026DeveloperDays CLAUDE.md?

Repository instructions for building Python scripts and automations that connect to SailPoint Identity Security Cloud, a cloud service for managing digital identities and access. They explain the project structure, API versions, and when to use the Python SDK or REST API.

Use them when developing or reviewing SailPoint integrations, API calls, SDK code, and automation scripts.

They provide the domain and version context needed to choose the correct SailPoint endpoint and implementation approach. This reduces the risk of using outdated API details.

How agutschow/2026DeveloperDays configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to agutschow/2026DeveloperDays. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/agutschow/2026DeveloperDays/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/agutschow/2026DeveloperDays

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/agutschow/2026developerdays/claude-md/github.svg)](https://agentmods.dev/instructions/agutschow/2026developerdays/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/agutschow/2026developerdays/claude-md"><img src="https://agentmods.dev/badge/instructions/agutschow/2026developerdays/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/agutschow/2026developerdays/claude-md"><img src="https://agentmods.dev/badge/instructions/agutschow/2026developerdays/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,316 This file is loaded in full into every session.

When invoked 1,316 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01316	$0.01316
Opus 5.5	$0.00526	$0.00526
Sonnet 5.5	$0.00263	$0.00263
Haiku 4.5	$0.00132	$0.00132

Measured 2mo ago against content hash 51333d5147a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

CLAUDE.md · 145 lines

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 — run git pull to stay current
src/ — Python scripts for each scenario
docs/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 /latest unconditionally.
Ongoing integrations: /latest is 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.

Read the full file on GitHub · 145 lines

Changes

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.

2mo ago First seen · 145 lines · 1,316 tokens per session scan A 51333d5147a6

Subscribe to this mod's changes

2026DeveloperDays CLAUDE.md is an instructions file published in the GitHub repository agutschow/2026DeveloperDays (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0053 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-08-31.

2026DeveloperDays CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
2026DeveloperDays CLAUDE.mdagutschow/2026DeveloperDays	Instructions file	2	6mo ago	MIT	A	1,316	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	144k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	150k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,086	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	281k	2d ago	MIT	A	4,335	Codex, OpenCode

2026DeveloperDays: Instructions file for Claude Code