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/rmjosea/agentic-sdlc-kit/agents-mdgit clone --depth 1 https://github.com/rmjosea/agentic-sdlc-kitWhat 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.01539 | $0.01539 |
| Opus 5 | $0.00770 | $0.00770 |
| Sonnet 5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
agentic-sdlc-kit AGENTS.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 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.
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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Engineering Contract
Purpose
Use this repository's skills to move from an idea to reviewed software with the least process that still produces reliable results.
Core behavior
- Think before editing. Inspect relevant code and evidence first.
- Surface material assumptions; never silently decide an ambiguous requirement.
- Prefer the simplest solution that fully meets the accepted need.
- Do not add unrequested features or speculative extensibility.
- Make surgical changes. Do not refactor unrelated code.
- Find root causes. Do not hide failures with workarounds.
- Define observable success before implementation.
- Run the relevant verification and report actual results.
- Never claim completion when required checks are failing or were not run.
- Preserve user changes and stop when scope or ownership is unclear.
Human decision protocol
Apply this protocol whenever a human decision is materially required.
- Ask exactly one question at a time.
- Explain the decision in plain, self-contained language.
- Do not combine independent decisions in one question.
- Offer two to four genuinely distinct options when useful.
- State the main consequence or trade-off of each option.
- Mark one option as Recommended and explain why it best fits the evidence.
- Allow a free-form answer when the listed options do not fit.
- After related decisions, summarize what is confirmed before continuing.
Ask when the answer could materially change scope, behavior, architecture, security, cost, user experience, reversibility, or the implementation plan. Do not interrupt for a trivial, reversible, repository-standard decision. Record such decisions with a concise rationale instead.
Workflow
The workflow is a set of composable gates, not a mandatory pipeline. Use the least durable process that safely preserves intent, evidence, and recoverability.
idea -> shape-idea -> write-spec -> plan -> decompose-tasks -> implement -> review
shape-idea: clarify conversationally; write no files.write-spec: persist approved product behavior as one or more cohesive specs.plan: resolve technical decisions and define the implementation design.decompose-tasks: turn an approved plan into an executable dependency graph.implement: complete one bounded direct, artifact-backed, or task-backed outcome using short feedback loops.review: assess intent conformance and engineering quality independently.create-skill: create or improve skills without bloating agent context.
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.
- 2d ago First seen · 163 lines · 1,539 tokens per session scan A b4d5f7d81c26
agentic-sdlc-kit AGENTS.md is an instructions file published in the GitHub repository rmjosea/agentic-sdlc-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,539 tokens to every session, about $0.0077 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
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.