Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/studioKjm/ai-harness-templatenpx agentmods add commands/studiokjm/ai-harness-template/rfc-linkWrote 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/studiokjm/ai-harness-template/rfc-link)<a href="https://agentmods.dev/commands/studiokjm/ai-harness-template/rfc-link"><img src="https://agentmods.dev/badge/commands/studiokjm/ai-harness-template/rfc-link.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.1 | $0.00025 | $0.01107 |
| Opus 5 | $0.00013 | $0.00553 |
| Sonnet 5 | $0.00005 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
rfc-link 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 8d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rfc-link — Link Working Code to an RFC
Tell the gate "this big change is OK because RFC X authorized it."
When to use
- Working on a PR that exceeds the RFC threshold (>500 LOC per file or >1000 total)
- File touches a path in
always_required_paths(auth, migrations, etc.) - Want to suppress the rfc-driven gate warning for a legitimate change
Usage
/rfc-link <rfc-id> --files F1 [F2 ...] [--modules M1 [...]]
/rfc declare-pr --rfc-id RID --pr-files F1 [F2 ...]
Both forms update the same data — link is more general (modules + files), declare-pr is specific to "the files in my current PR".
Prerequisites
- Target RFC must be in
acceptedstate (script blocks otherwise) - File paths should be repo-root relative
Instructions
Step 1 — Find the relevant accepted RFC
python3 .harness/methodologies/rfc-driven/scripts/rfc.py list --status accepted
If no relevant RFC exists, stop and create one — don't link to a tangentially related RFC.
Step 2 — Link files
# Add specific files
python3 .harness/methodologies/rfc-driven/scripts/rfc.py \
link rfc-2026-04-30-eventbus-replacement \
--files src/events/publisher.ts src/events/consumer.ts
# Add a whole module
python3 .harness/methodologies/rfc-driven/scripts/rfc.py \
link rfc-2026-04-30-eventbus-replacement \
--modules src/events/
# Both at once
python3 .harness/methodologies/rfc-driven/scripts/rfc.py \
link rfc-2026-04-30-eventbus-replacement \
--files src/main.ts \
--modules src/events/ src/messaging/
Step 3 — Declare current PR's files (convenience)
If you're working on a feature branch and want to link all currently changed files:
# List changed files in your branch
git diff --name-only main...HEAD > /tmp/pr-files.txt
# Declare them
python3 .harness/methodologies/rfc-driven/scripts/rfc.py \
declare-pr \
--rfc-id rfc-2026-04-30-eventbus-replacement \
--pr-files $(cat /tmp/pr-files.txt)
Step 4 — Verify the gate now allows the change
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.
- 8d ago First seen · 127 lines · 25 tokens per session scan A 30de325399bb
rfc-link is a command published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,107 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
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.
step1-preflight-check
Pipeline Step 1 — Pre-flight checks before plan hardening. Verifies git state, roadmap link, plan file, guardrails, and domain-specific instruction files.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
release-tag
Create and push a version tag after a release PR has been merged.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
next
Suggest the most likely next workflow action based on current context.