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/zeeshanhanif/agentic-sdlc-kit/claude-mdgit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/claude-md)<a href="https://agentmods.dev/instructions/zeeshanhanif/agentic-sdlc-kit/claude-md"><img src="https://agentmods.dev/badge/instructions/zeeshanhanif/agentic-sdlc-kit/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.07787 | $0.07787 |
| Opus 5 | $0.03893 | $0.03893 |
| Sonnet 5 | $0.01557 | $0.01557 |
| Haiku 4.5 | $0.00779 | $0.00779 |
Grade A, and why
agentic-sdlc-kit 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 5d 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Working notes for agents editing this repository. Not user documentation —
that's README.md, and it must be updated whenever the facts here
change.
1. What you are working on
This repo contains twelve Agent Skills (open SKILL.md standard) that form one
SDLC pipeline. There is no application code, build system, test suite, or
linter. The deliverable is instruction content loaded into an agent's context at
runtime.
Consequences for how you work here:
- "Correctness" means the instructions are unambiguous, well-scoped, and trigger reliably — not that something compiles. You cannot run these skills to test them; review by reading.
- Every token costs.
SKILL.mdis loaded on every invocation. Prefer deleting a sentence to adding one. Depth goes inreferences/, read on demand. - The twelve skills are coupled. Changing what one emits ripples into how the next ingests it. §4 lists the couplings; check them before editing any skill.
- Never write project-specific lessons back into a skill folder. Skills emit
project-owned artifacts (
scaffold-notes.md,deployment-notes.md, …); that's where run-specific knowledge lives.
2. Layout and install-path invariants
skills/<skill-name>/
├── SKILL.md # required: frontmatter + the workflow
└── references/ # optional: guides SKILL.md tells the agent to read on demand
Load-bearing and easy to break:
skills/<name>/SKILL.mdis the flat layout theskillsCLI discovers. Moving a skill out ofskills/breaksnpx skills add <repo> --skill <name>.- Frontmatter has exactly two keys:
nameanddescription.namemust equal the directory name and the--skillargument. Nolicense:key, no per-file headers —SKILL.mdcontent enters an agent's context on every invocation. descriptionis the only thing an agent sees when deciding to invoke the skill. It carries the trigger phrases and the "use this when…" intent. Editing it changes when the skill fires — treat as load-bearing, never boilerplate.- The CLI resolves against the pushed GitHub repo (
zeeshanhanif/agentic-sdlc-kit), not the local tree. Layout/frontmatter changes reach users only after a push. - Manual install lands at
~/.claude/skills/<name>/SKILL.md(personal) or.claude/skills/<name>/SKILL.md(project). One level too deep silently fails. - Renaming a skill directory or its frontmatter
namechanges the install command → update README's Install section and every example in lockstep.
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.
- 5d ago First seen · 549 lines · 7,787 tokens per session scan A fabccbbb989a
agentic-sdlc-kit CLAUDE.md is an instructions file published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 9d ago), licensed Apache-2.0. It adds 7,787 tokens to every session, about $0.0389 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
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).
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.
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.
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).