What is sruja-prime-task?

A command guide for preparing context before a Sruja task. It tells an agent how to inspect the relevant files, architecture documents, previous project decisions, and current project status.

Use it before planning or implementing work, especially when given a file path or issue, to identify the change's impact, constraints, and open questions.

It reduces the chance of planning changes without understanding the affected code or the project's existing rules.

sruja-prime-task — Command for Claude Code and Cursor by sruja-ai

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.

Clone the repo

git clone --depth 1 https://github.com/sruja-ai/sruja

Made for: Claude Code, Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-prime-task/github.svg)](https://agentmods.dev/commands/sruja-ai/sruja/sruja-prime-task)

Your own site

<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-prime-task"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-prime-task/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sruja-ai/sruja/sruja-prime-task"><img src="https://agentmods.dev/badge/commands/sruja-ai/sruja/sruja-prime-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 330 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00330
Opus 5	$0.00008	$0.00165
Sonnet 5	$0.00003	$0.00066
Haiku 4.5	$0.00002	$0.00033

Measured 9d ago against content hash 0d88c6fec284, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sruja-prime-task 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.

.cursor/commands/sruja-prime-task.md · 21 lines

What it actually says

You are working on the Sruja repo. Follow AGENTS.md (especially AI agent workflow).

Goal: Load enough context to plan or implement safely—without pasting huge unrelated trees.

Do this in order:

If the user gave a file path, run sruja focus --file <that path> from the repo root and summarize blast radius and constraints.
If they gave an issue URL or ID, restate acceptance criteria and link to any spec they mentioned.
Skim project / scope layer only: relevant docs/architecture/*.sruja, repo.sruja, or ADRs that bound this work. Do not pick final edit lists yet unless obvious.
Use narrow reads (search + open specific files) or Sruja MCP (.cursor/mcp.json) for architecture questions—avoid dumping entire crates into the transcript.
- On connect: use notifications/drift_state or call sruja_get_drift_state once.
- For “why did we…” / precedent: sruja_search_memory first.
- Follow .cursor/rules/sruja-context-host.mdc for prune and memory.
List open questions for the user (max 5). Ask them one batch or one at a time depending on what blocks planning.

Do not write implementation code until the user confirms scope or points you at an agreed plan artifact.

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.

9d ago First seen · 21 lines · 15 tokens per session scan A 0d88c6fec284

Subscribe to this mod's changes

sruja-prime-task is a command published in the GitHub repository sruja-ai/sruja (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 15 tokens to every session and 330 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.

Planning agent-loop agent-skills ai architecture developer-tools rust-lang

sruja-prime-task

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

arrange-workspace-flow-technical-context

plan

xray

check

review-drift

plan-feature