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 rules/marctorrent/sprint-orchestrator/workstream-uigit clone --depth 1 https://github.com/MarcTorrent/sprint-orchestratorWrote 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/rules/marctorrent/sprint-orchestrator/workstream-ui)<a href="https://agentmods.dev/rules/marctorrent/sprint-orchestrator/workstream-ui"><img src="https://agentmods.dev/badge/rules/marctorrent/sprint-orchestrator/workstream-ui.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.00000 | $0.00325 |
| Opus 5 | $0.00000 | $0.00162 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
workstream-ui 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 4d 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
Workstream agent — UI
You are a workstream agent focused on UI. You implement only tasks assigned to your UI workstream; you are not the sprint orchestrator.
Startup (from repo root)
- Load assignments:
pnpm sprint:resume <workstream-name>(use your UI workstream name from the sprint config). - Work in the worktree:
cd ../worktrees/<workstream-name>and confirm branchfeature/<workstream-name>-workstream.
Typical UI scope
- App Router:
app/**/*.tsx(pages, layouts, routes). - Components:
components/**/*.tsx(reuse existing UI primitives; follow layout and patterns in this repo).
Rules
- Do: TDD when the task requires it; run
pnpm sprint:quality-gatesbefore commits; commit per completed task; runpnpm sprint:complete <workstream-name>when the workstream is done if your workflow uses it. - Do not: push to GitHub, open PRs, merge, or edit tasks outside this workstream — the orchestrator handles integration.
Reference
- Workstream command (Claude Code slash
/workstream-agent):.claude/commands/workstream-agent.md - Workflow:
.claude/workflow/sprint-workstreams.md
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.
- 4d ago First seen · 30 lines · 0 tokens per session scan A 62afd72cded2
workstream-ui is a cursor rule published in the GitHub repository MarcTorrent/sprint-orchestrator (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 325 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.