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/rhecosystemappeng/sdlc-plugins/claude-mdgit clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-pluginsWhat 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.00494 | $0.00494 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
sdlc-plugins 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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sdlc-plugins
Documentation
- docs/methodology.md — Core principles and SDLC phases
- docs/workflow.md — Execution workflow (plan, implement, verify) and skill invocation
- docs/tools.md — MCP server catalog (Jira, Figma, Serena)
- docs/conventions-spec.md — Cross-repo workflow conventions and per-repo template reference
- docs/constraints.md — Deterministic rules for agent behavior
- docs/project-config-contract.md — Project Configuration contract for CLAUDE.md
- docs/metrics.md — Workflow metrics and measurement
- docs/releasing.md — Release process and changelog
Version Management
The plugin version must be kept in sync in two files:
plugins/sdlc-workflow/.claude-plugin/plugin.json— the plugin manifest (required by CI validation).claude-plugin/marketplace.json— the marketplace registry (required for relative-path plugins per Claude Code docs)
When bumping the version, update both files together.
Project Configuration
Repository Registry
| Repository | Role | Serena Instance | Path |
|---|---|---|---|
| sdlc-plugins | Claude Code plugin | — | ./ |
Jira Configuration
- Project key: TC
- Cloud ID: 2b9e35e3-6bd3-4cec-b838-f4249ee02432
- Feature issue type ID: 10142
- Git Pull Request custom field: customfield_10875
- GitHub Issue custom field: customfield_10747
Code Intelligence
No Serena MCP servers are configured. Code intelligence is not available.
Limitations
No limitations known — no Serena instances configured.
Bug Configuration
- Bug issue type ID: 10016
- Bug template: docs/templates/bug-template.md
- Bug-to-Task link type: Blocks
Hierarchy Configuration
- Default epic grouping strategy: by-sub-feature
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.
- 3d ago First seen · 56 lines · 494 tokens per session scan A 738c29b262a9
sdlc-plugins CLAUDE.md is an instructions file published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (11 stars, last pushed 9d ago), licensed Apache-2.0. It adds 494 tokens to every session, about $0.0025 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-30.
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.