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/consensys/doc.linea/terminologygit clone --depth 1 https://github.com/Consensys/doc.lineaWhat 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.00000 | $0.00390 |
| Opus 5 | $0.00000 | $0.00195 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
terminology 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 2d 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
Terminology
Casing of common terms
- Use "dapp" rather than "dApp" or "DApp", and capitalize like any other noun.
- Use "onchain" rather than "on-chain" or "on chain", and capitalize like any other noun.
- Use "offchain" rather than "off-chain" or "off chain", and capitalize like any other noun.
- Use lowercase "web2" and "web3" (never "Web2"/"Web3"), except at the start of a sentence.
Linea vs. Lineth naming
Linea and Lineth are related but distinct terms, and getting them right matters for technical accuracy:
- Linea is the public Mainnet network, brand, token, tokenomics, governance, and the Linea SDK.
- Lineth is the open-source ZK-rollup stack, protocol, codebase, components, onchain contracts, and tooling that Linea Mainnet and other networks are built on.
Do not assert which term applies to a given page from memory. The canonical explanation,
including the tab-to-product mapping (which tabs document Linea vs. Lineth), lives at
Linea and Lineth (docs/protocol/linea-vs-lineth.mdx). Read
that page first, and match the naming already used on neighboring pages in the same
section.
Where a page already uses a term consistently, keep matching it rather than introducing a new term. If you're unsure whether a name is final, leave the existing wording in place and note your question in the pull request description rather than guessing.
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.
- 2d ago First seen · 35 lines · 0 tokens per session scan A d3651249f2ea
terminology is a cursor rule published in the GitHub repository Consensys/doc.linea (474 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 390 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
documentation
Documentation discovery index for Lineth monorepo.
docstruct
Keep project documentation clear, non-duplicated, source-of-truth driven, and token-efficient.
with-jsdoc
Creating and Editing JSDoc comments.
api
Remember: APIs are forever. Design them carefully, version them properly, and never break backward compatibility.
controllers
Remember: Controllers are just the translation layer between HTTP and your application. Keep them simple and let other layers handle complexity.
performance
Remember: Premature optimization is the root of all evil. Profile first, optimize what matters, and keep solutions maintainable.