apply

A coding step that implements a change according to an application-level requirement contract, a written agreement describing what the code must do.

In plain words
What is it for?
It reads the requirement and application technology guidance, makes the code changes, and leaves the resulting Git diff for the following validation step.
Why use it?
It keeps implementation tied to the approved requirements and technical standards, making deviations visible instead of silently changing the plan.

Command

Install

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.

agentmods
npx agentmods add commands/alisunstar/opensunstar/apply
Clone the repo
git clone --depth 1 https://github.com/alisunstar/OpenSunstar
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 136 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00136
Opus 5 $0.00000 $0.00068
Sonnet 5 $0.00000 $0.00027
Haiku 4.5 $0.00000 $0.00014

Measured yesterday against content hash f287f9adf148, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

apply 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 yesterday.

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.

rd-protocol/commands/apply.md · 19 lines

What it actually says

/rd:apply — 代码实现

阶段 4:按应用级 requirement 契约编码实现。

先读

  • .specs/<change-id>/applications/{app}/requirement.md(契约)
  • knowledge/applications/{app}/tech/(技术规范)

执行

  • 按契约实现代码
  • 遵循 tech 规范
  • 不偏离契约——若需偏离,标记后回 validate 处理

产物

代码变更(git diff)

人工确认

否 — 实现后直接进入 validate 对账。

Changes

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.

  1. yesterday First seen · 19 lines · 0 tokens per session scan A f287f9adf148

Subscribe to this mod's changes

apply is a command published in the GitHub repository alisunstar/OpenSunstar (40 stars, last pushed 18d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 136 tokens. 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.