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/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/build-test-commands)<a href="https://agentmods.dev/rules/yu-iskw/llmops-demo-ts/build-test-commands"><img src="https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/build-test-commands/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/yu-iskw/llmops-demo-ts/build-test-commands"><img src="https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/build-test-commands.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.00262 | $0.00262 |
| Opus 5 | $0.00131 | $0.00131 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
build-test-commands 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
Development Commands
This project uses pnpm as its package manager. Below are common commands for development tasks:
-
Build Project: To build all packages in the workspace:
pnpm buildThis runs the "build" script defined in the root
package.json, which recursively builds all workspace packages. -
Run Tests: To run tests for the project:
pnpm testNote: The current
testscript inpackage.jsonis a placeholder:"echo \"Error: no test specified\" && exit 1". You may need to update this script in individual packagepackage.jsonfiles for actual testing. -
Format Code: To format code using
trunk fmt:pnpm format # or to format all files pnpm format:all -
Lint Code: To lint code using
trunk check:pnpm lint # or to lint all files pnpm lint:all # or to lint for security issues pnpm lint:security
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 · 45 lines · 262 tokens per session scan A 377ab8df4bf3
build-test-commands is a cursor rule published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 262 tokens to every session, about $0.0013 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-09-04.
Other cursor rules, from other repositories
design
All tasks related to updating frontend components, CSS, and general styling.
general
No need to run the app. It's already up. i.e. no bun dev or bun run build.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI and config schema sync before lint, final checks.
code-style
Formatting, lint, comments language.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
shadcn-tailwind-guide
A guide to building new components with shadcn/ui and Tailwind CSS, a utility-based system for styling interfaces.