008-office-ui-events

008-office-ui-events is a cursor rule for Cursor from phuoctrung-ppt/ai-sdlc-workflow. It costs 391 tokens per session, scanned A, original, MIT.

A rule for sending coding-agent activity events to an office-style interface when an .aisdlc directory exists. Events can report statuses such as working, waiting, done, error, or idle, along with task and workflow details.

In plain words
What is it for?
Use it to emit turn-start and turn-end events, report task progress, and include token totals when they are known or estimated.
Why use it?
It gives the interface a record of agent activity and can track token use by workflow.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .cursor/scripts/office-event.py \.

Good fit Use it to emit turn-start and turn-end events, report task progress, and include token totals when they are known or estimated.

Compare 6 cursor rules from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflow
agentmods
npx agentmods add rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events

Made for: 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.

agentmods badge for 008-office-ui-events

README.md
[![agentmods](https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events/github.svg)](https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events)
Your own site
<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events/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.

agentmods 80×15 button for 008-office-ui-events

Your own site · 80×15
<a href="https://agentmods.dev/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events"><img src="https://agentmods.dev/badge/rules/phuoctrung-ppt/ai-sdlc-workflow/008-office-ui-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 391 This file is loaded in full into every session.
When invoked 391 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00391 $0.00391
Opus 5 $0.00196 $0.00196
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

Measured 8d ago against content hash 17d2c4a585c5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

008-office-ui-events 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.

.cursor/rules/008-office-ui-events.mdc · 52 lines

What it actually says

Office UI events

If .aisdlc/ exists, emit on every agent turn start/end.

python3 .cursor/scripts/office-event.py \
  --agent <agent-id> \
  --status working|waiting|done|error|idle \
  --task "<short task>" \
  --phase <phase> \
  --workflow <module-or-workflow-id> \
  [--tokens N] [--tokens-in N] [--tokens-out N]

Token audit (required on done when known)

When finishing a turn / phase, if you can estimate or read usage:

python3 .cursor/scripts/office-event.py \
  --agent backend-worker \
  --status done \
  --task "API done" \
  --phase implement-backend \
  --workflow {feature_name} \
  --tokens 25000 \
  --tokens-in 19000 \
  --tokens-out 6000
  • --workflow groups costs for the TOKEN AUDIT panel (per module).
  • Tokens accumulate in .aisdlc/state.json and .aisdlc/benchmarks.json.
  • Prefer real usage meters when the host exposes them; otherwise estimate and label in --detail as est.

Status

Status When
working Start task
waiting Blocked
done Success (+ tokens when possible)
error Failed
idle Clear desk

UI: ai-sdlc uihttp://127.0.0.1:9669 — click a desk to inspect task + tokens; LIVE BOARD updates in place per agent.

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. 8d ago First seen · 52 lines · 391 tokens per session scan A 17d2c4a585c5

Subscribe to this mod's changes

008-office-ui-events is a cursor rule published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 2d ago), licensed MIT. It adds 391 tokens to every session, about $0.0020 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-31.