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/lazylagom/context-compose-mcp/assets-rulegit clone --depth 1 https://github.com/lazylagom/context-compose-mcpWrote 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/lazylagom/context-compose-mcp/assets-rule)<a href="https://agentmods.dev/rules/lazylagom/context-compose-mcp/assets-rule"><img src="https://agentmods.dev/badge/rules/lazylagom/context-compose-mcp/assets-rule.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 | $0.00030 | $0.00030 |
| Opus 5 | $0.00015 | $0.00015 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
assets-rule 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
assets 디렉토리에 있는 파일의 모든 내용은 영어로만 작성한다
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 · 7 lines · 30 tokens per session scan A ce04b2a2ca7e
assets-rule is a cursor rule published in the GitHub repository lazylagom/context-compose-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 30 tokens to every session, about $0.0002 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.
Other cursor rules, from other repositories
auth
Auth architecture, middleware chain, and auth-specific coding standards.
tableau-mcp
Tableau MCP project context, architecture overview, and core principles.
tools
MCP tool development patterns — factory pattern, base class, callbacks, and descriptions.
testing
Testing standards — Vitest framework, test organization, mocking patterns.
cursorrules
Cursor rule "cursorrules" from dunialabs/peta-core, covering cursor ide scheduling rules, role positioning, task assignment rules, → assign to claude code (precise, controllable) and → assign to codex (complex, large-scale).
chrono-mcp-standards
Chrono MCP Project Standards and Guidelines.