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/yu-iskw/llmops-demo-ts/tech-stackgit 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/tech-stack)<a href="https://agentmods.dev/rules/yu-iskw/llmops-demo-ts/tech-stack"><img src="https://agentmods.dev/badge/rules/yu-iskw/llmops-demo-ts/tech-stack.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.1 | $0.00088 | $0.00088 |
| Opus 5 | $0.00044 | $0.00044 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
tech-stack 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.
What it actually says
Tech Stack
This project uses:
- Package Manager: pnpm
- Node.js Version: (read from .node-version)
- Backend: tsoa
- Frontend: Vue.js
- LLM Provider: Gemini API and Gemini on Vertex AI (using google/genai)
- CLI Framework: Commander.js (for building command-line interfaces)
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.
- yesterday First seen · 14 lines · 88 tokens per session scan A 9edf455a6556
tech-stack is a cursor rule published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 88 tokens to every session, about $0.0004 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.
frontend-rules
如需详细组件/页面开发示例，可参考 src/pages/chat/index.vue、src/components/NotebookArea.vue、src/components/ui/button/Button.vue 等文件。.
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
Cursor rule "backend-rules" from jihe520/MathModelAgent, covering 后端开发规则, 目录结构, 技术栈, 运行环境 and 主要流程.