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 commands/ai-sdlc-framework/ai-sdlc/rfc-initgit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/commands/ai-sdlc-framework/ai-sdlc/rfc-init)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/rfc-init"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/rfc-init.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.00029 | $0.01002 |
| Opus 5 | $0.00015 | $0.00501 |
| Sonnet 5 | $0.00006 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
rfc-init 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold a new adopter RFC from the canonical framework-rfc.md
template. Writes to <adopter-repo>/rfcs/<slug>.md by default; honours
.ai-sdlc/adopter-authoring.yaml's rfc-scaffold.rfcDir override per
RFC-0036 OQ-4, and respects an explicit --rfc-dir flag override.
Per RFC-0036 OQ-5 + OQ-12 (resolved 2026-05-16)
- One template —
framework-rfc.md. Variants (architecture / product-decision / retrospective) are a future Decision in the Catalog if adopter demand justifies the split. Cognitive load < flexibility for v1. - Dual surface. This slash command and the underlying
ai-sdlc rfc initCLI ship together — both shell out to the samepipeline-cli/bin/cli-rfc.mjs initentry point, so there is one source of truth for slug validation, path resolution, and template rendering.
Phase scope (Phase 2 of RFC-0036)
- ✓
init <slug>CLI + slash command - ✓ Single
framework-rfc.mdtemplate - ✓ Default path
<adopter-repo>/rfcs/<slug>.md+adopter-authoring.yamloverride - ✓ Tutorial walkthrough (
docs/tutorials/11-authoring-adopter-rfc.md) - ✗ Decision Catalog cross-linking (Phase 9 / AISDLC-334 — already shipped via
cli-rfc index) - ✗ RFC variants (deferred — future Decision in the catalog)
Usage
node pipeline-cli/bin/cli-rfc.mjs init <slug> [--title <title>] [--author <name>] [--rfc-dir <path>] [--force] [--template <path>] [--format <text|json>]
$ARGUMENTS is the slug + any flags. Slug rules: lowercase
alphanumeric + hyphens, no leading/trailing hyphens, no path
separators, max 80 chars.
ARGS="${ARGUMENTS:-}"
if [[ -z "$ARGS" ]]; then
echo "Usage: /ai-sdlc rfc-init <slug> [--title <title>] [--author <name>] [--rfc-dir <path>] [--force]"
exit 1
fi
# Pass the operator's args straight through. The CLI handles slug
# validation, conflict detection, and template materialisation.
node pipeline-cli/bin/cli-rfc.mjs init $ARGS
Output
- Success (text mode): absolute destination path + resolved
rfcDir,rfcDirSource,template,slug,title,createdAt, and a three-step "next steps" reminder. - Success (
--format json): structured envelope withok: true, the resolved fields above, pluscreated: true. - Failure: non-zero exit + a single stderr line explaining the
blocker (invalid slug, existing destination without
--force, missing template). The CLI does NOT partial-write — the file is either fully materialised or untouched.
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 · 87 lines · 29 tokens per session scan A d0f9884fa2de
rfc-init is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (92 stars, last pushed 10d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,002 once invoked, about $0.0001 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 commands, from other repositories
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
research
Research a technical or product question.
session-stop
Stop recording and save this agent session to the project ledger.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
ox-session-pause
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Suspend the current session recording. Local cache continues to receive entries, but the upload at stop time will exclude the suspended range.
au-aescsf
You are an enterprise architect generating an Australian Energy Sector Cyber Security Framework (AESCSF) maturity assessment for an Australian energy-sector project, asset, market interface, OT environment, DER platform, or regulated energy business capability.