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/zhangdszq/teamclawWrote 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/zhangdszq/teamclaw/ts-no-unused)<a href="https://agentmods.dev/rules/zhangdszq/teamclaw/ts-no-unused"><img src="https://agentmods.dev/badge/rules/zhangdszq/teamclaw/ts-no-unused/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/rules/zhangdszq/teamclaw/ts-no-unused"><img src="https://agentmods.dev/badge/rules/zhangdszq/teamclaw/ts-no-unused.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.00000 | $0.00385 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
ts-no-unused 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 10d 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
禁止未使用的变量和参数
项目 tsconfig 开启了 noUnusedLocals 和 noUnusedParameters，未使用的声明会导致构建失败。
规则
每次修改 .ts / .tsx 文件后，必须检查：
- 新增的 import、变量、参数、解构字段是否都被使用
- 删除功能代码后，相关的 import 和参数是否已一并清理
- 接口/类型中移除了某个字段时，所有引用该字段的解构也要同步清理
常见修复方式
// ❌ BAD — 解构了但未使用
const { used, unused } = props;
// ✅ GOOD — 只解构需要的
const { used } = props;
// ❌ BAD — import 后未使用
import { helperA, helperB } from './utils';
// 只用了 helperA
// ✅ GOOD
import { helperA } from './utils';
// ❌ BAD — 参数未使用
function handler(req: Request, res: Response, next: NextFunction) {
res.send('ok');
}
// ✅ GOOD — 用下划线前缀标记有意忽略
function handler(_req: Request, res: Response, _next: NextFunction) {
res.send('ok');
}
检查清单
- 新增的 import 全部被引用
- 解构的字段全部被使用
- 函数参数全部被使用（不需要的加
_前缀） - 删除代码后相关的 import 已清理
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.
- 10d ago First seen · 52 lines · 0 tokens per session scan A 9739e35a0c8d
ts-no-unused is a cursor rule published in the GitHub repository zhangdszq/teamclaw (113 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 385 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-30.
Other cursor rules, from other repositories
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
nextjs-typescript-app-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript integration.
ts
A set of TypeScript coding rules covering types, naming, file organization, error handling, and strict type checking. TypeScript is JavaScript with checks that help catch many mistakes before the program runs.
platform-pattern-2-filesystem-operations
Cursor rule "platform-pattern-2-filesystem-operations" from PaulJPhilp/EffectPatterns, covering platform pattern 2: filesystem operations and example.
handle-unexpected-errors-by-inspecting-the-cause
Cursor rule "handle-unexpected-errors-by-inspecting-the-cause" from PaulJPhilp/EffectPatterns, covering handle unexpected errors by inspecting the cause and example.
modeling-tagged-unions-with-datacase
Cursor rule "modeling-tagged-unions-with-datacase" from PaulJPhilp/EffectPatterns, covering modeling tagged unions with data.case and example.