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.
git clone --depth 1 https://github.com/sruja-ai/srujaWrote 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/sruja-ai/sruja/sruja-implement-from-plan)<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-implement-from-plan"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-implement-from-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-implement-from-plan"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-implement-from-plan.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00269 |
| Opus 5 | $0.00007 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
sruja-implement-from-plan 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 9d 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.
What it actually says
Session rule: Treat this as implementation-only. The user should have a frozen written plan (issue section, plan.md, or pasted markdown). If they only have a vague goal, stop and tell them to run sruja-plan-feature first or paste the plan.
Steps:
- Read the plan once. List the plan’s task order as a todo list and execute in order.
- Follow
AGENTS.mdand.cursor/rules/sruja-dev.mdc. Respect crate boundaries and existing patterns. - Implement the smallest coherent diffs. No drive-by refactors outside the plan.
- Run the validation section from the plan. If the plan omitted commands, run
just check(ormake check) from repo root. For.srujaedits, runsruja linton touched files. - Summarize: files changed, tests run, any plan deviation (there should be none; if you had to deviate, say why explicitly).
If the conversation already contains a long exploration before this command, prefer starting a new chat, pasting only the plan + paths—per AGENTS.md session hygiene.
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.
- 9d ago First seen · 16 lines · 14 tokens per session scan A 8f2c28bc7eb2
sruja-implement-from-plan is a command published in the GitHub repository sruja-ai/sruja (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 269 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
arrange-workspace-flow-technical-context
Phase 4 Technical context of arrange-workspace-flow.
plan
Planning, brainstorming, architecture, and refactoring strategies.
xray
Zero-config X-ray of this repo's real architecture — map, living docs, and evolution feed. No rules required.
check
Fail on NET-NEW architecture violations only — the same ratchet ArchSteer runs in CI, run right now.
review-drift
Walk the VibeFrame drift inbox and resolve each finding (fix / accept / dismiss).
plan-feature
Plan and implement a feature through the VibeFrame model (context → declare → implement → link → validate).