csa-skilljar CLAUDE.md

Instructions for Claude Code when working in the csa-skilljar repository. They explain the Python library, its local MCP server, project structure, design rules, and important limits around Skilljar writes.

In plain words
What is it for?
Use them before proposing or making changes to csa-skilljar, especially changes involving API routing, credentials, data handling, or writes.
Why use it?
They help an agent avoid silent architectural mistakes and avoid claiming that real Skilljar write operations have been verified. They also point to the repository's authoritative design document.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/cloudsecurityalliance/csa-skilljar/claude-md
Clone the repo
git clone --depth 1 https://github.com/CloudSecurityAlliance/csa-skilljar
Per session 4,180 This file is loaded in full into every session.
When invoked 4,180 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.04180 $0.04180
Opus 5 $0.02090 $0.02090
Sonnet 5 $0.00836 $0.00836
Haiku 4.5 $0.00418 $0.00418

Measured 2d ago against content hash c42b34ecb634, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

csa-skilljar CLAUDE.md scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://api.skilljar.com/v2/openapi.json | jq '.paths | keys | length'
CLAUDE.md · 274 lines

How it starts

The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

Guidance for Claude Code (claude.ai/code) when working in this repository.

What this repository is

csa-skilljar — a Python library (import name csa_skilljar) and local stdio MCP server over both Skilljar REST APIs. It reproduces the official Skilljar MCP server's 73-tool surface exactly, then adds the capabilities that exist only in v1.

Status: shipped and in use. All seventeen roadmap blocks are on main112 tools (84 over v2, 27 over v1, plus demonstration_plan) across 37 modules in src/, with 52 test files. Released to PyPI through v0.15.0; installed on staff machines by DesktopSetup.

Still true, and the thing to keep honest: no write has ever run against real Skilljar. Every read is exercised against the production organization; the write half has only ever run against FakeBackend. That is what v1.0.0 waits on — see WAITING-FOR-003. Do not describe writes as verified.

Where things live

  • docs/superpowers/specs/2026-08-26-csa-skilljar-design.md — the authoritative design. Read it before proposing anything. Architecture, routing rule, credential model, error taxonomy, phasing, and three appendices of probe-verified facts.
  • specs/ — upstream OpenAPI snapshots, fetched 2026-08-26. skilljar-v1-openapi.yml (3.0.3, 160 paths / 340 ops) and skilljar-v2-openapi.json (3.1.0, 44 paths / 82 ops). These are snapshots of someone else's moving target — see "Upstream drift" below. Already drifted: live v2 had 46 paths on 2026-08-31. The two new ones are /v2/assets/ and /v2/assets/{id} — the first time the ADR-002 retirement trigger has fired. See TODO.md.
  • analysis/ — the 66-entity reconciliation of both APIs (entity-inventory.csv/.json), the live OAuth scope catalogue, and a browsable surface map.
  • docs-html/ — the rendered vendor doc pages, kept for provenance. Low value; the specs are the useful artifact.
  • GOALS.md / BUSINESS-CASE.md — what success is, and the honest argument that this project should get smaller over time. Read before proposing scope changes.
  • TODO.md — the index of ALL open work, per the CINO todo-index convention. Sweeping this plus open GitHub Issues finds everything. It also carries a consideration pile of things deliberately not committed to — check it before proposing a "missing" feature.
  • DECISIONS-ADR.md + DECISIONS-ADR/ — seven technical decisions with their rejected alternatives. ADR-002 (routing) and ADR-004 (no version in tool names) are load-bearing; do not contradict them without a superseding ADR.
  • DECISIONS-PRD.md + DECISIONS-PRD/ — scope, audience, and explicit out-of-scope.
  • SECURITY-RESOURCES.md — exposure surface and the prompt-injection threat. Constrains any change that surfaces course content to a model.
  • DATA-RESOURCES.md / DATA-NEEDS.md — what data is handled and what is deliberately never stored. No caching, no persistence — proposing either changes the security posture and needs its own ADR.
  • WAITING-FOR.md + WAITING-FOR/ — external conditions with observable triggers. 001 is the retirement trigger for each v1 family; 002 blocks all of Phase 1.
  • FRICTION.md + FRICTION/ — friction log. Low bar: if it is an annoyance for a human or an AI, log it.
  • OPERATIONAL-RESOURCES.md — the one recurring job (check_upstream.py). Check its "Next review" date against today when working here.
  • RACI.md — authority by domain. Note: credential issuance is never delegated to AI.
  • CHATGPT.md / GEMINI.md — pointers to this file, deliberately not copies.

Read the full file on GitHub · 274 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.

  1. 2d ago First seen · 274 lines · 4,180 tokens per session scan A c42b34ecb634

Subscribe to this mod's changes

csa-skilljar CLAUDE.md is an instructions file published in the GitHub repository CloudSecurityAlliance/csa-skilljar (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 4,180 tokens to every session, about $0.0209 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens