team-flow-unit

A development lane for unit tests using Vitest, a JavaScript and TypeScript testing tool. It connects the `/unit` path with the `/grill-unit` path.

In plain words
What is it for?
Use it to organise or route Vitest unit-test tasks through the specified development and review paths.
Why use it?
It gives unit-test work a defined place and workflow instead of leaving test tasks mixed with other development work.

Cursor rule

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 rules/shanyucoder/forgekit/team-flow-unit
Clone the repo
git clone --depth 1 https://github.com/ShanYuCoder/forgekit
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00326
Opus 5 $0.00000 $0.00163
Sonnet 5 $0.00000 $0.00065
Haiku 4.5 $0.00000 $0.00033

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

Security

Grade A, and why

team-flow-unit 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.

harness/fe/rules/team-flow-unit.mdc · 28 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 28 lines · 0 tokens per session scan A 640edfe30038

Subscribe to this mod's changes

team-flow-unit is a cursor rule published in the GitHub repository ShanYuCoder/forgekit (0 stars, last pushed 2d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 326 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.