Borrowing it
Nothing to install: this file belongs to Consensys/doc.linea. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Consensys/doc.linea/main/.agents/skills/author-doc-page/SKILL.mdgit clone --depth 1 https://github.com/Consensys/doc.lineaWrote 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/skills/consensys/doc.linea/author-doc-page)<a href="https://agentmods.dev/skills/consensys/doc.linea/author-doc-page"><img src="https://agentmods.dev/badge/skills/consensys/doc.linea/author-doc-page.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01086 |
| Opus 5 | $0.00024 | $0.00543 |
| Sonnet 5 | $0.00010 | $0.00217 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
author-doc-page 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author a docs.linea.build page
Help create a new documentation page that follows docs.linea.build's editorial standards from the start.
When to use
- You need to scaffold a new page or write a first draft.
- You're helping a contributor who isn't a professional writer produce content that meets the documentation team's expectations (for example, an ecosystem partner documenting their integration).
Inputs
Ask the user for anything they haven't already provided:
- Tab: which tab is this for? (Linea Mainnet, Lineth Stack, Protocol, Reference, Changelog)
- Content type: concept/explanation, how-to guide, reference, or tutorial?
- Topic: what is the page about?
- File path: where should the file live? Suggest one based on the tab and topic if the user doesn't specify (see the directory table in README.mdx).
- Source material: what code, spec, PR, or other reference verifies the content?
Step 1: Confirm an issue exists, then load the relevant rules
Per .cursor/rules/contributor-workflow.mdc, an issue should exist for this change
before work starts. Ask the user whether one's already open; if not, point them to
CONTRIBUTING.md and the templates in .github/ISSUE_TEMPLATE/
so they can open one before you invest time scaffolding and drafting. This matters most
for ecosystem/partner contributors.
Then read these rule files before scaffolding, and apply them by reference rather than restating them in the draft:
.cursor/rules/contributor-workflow.mdc: issue-first workflow, redirects, PR hygiene..cursor/rules/content-structure.mdc: tab, audience, tone, and page-structure conventions..cursor/rules/editorial-voice.mdc: voice, heading style, and the[VERIFY]marker convention..cursor/rules/terminology.mdc: casing, Linea vs. Lineth naming, and component capitalization..cursor/rules/markdown-formatting.mdc: frontmatter, links, and file conventions.
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.
- 8d ago First seen · 102 lines · 49 tokens per session scan A a707f6f427b4
author-doc-page is a skill published in the GitHub repository Consensys/doc.linea (474 stars, last pushed 11d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,086 once invoked, 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-30.
Other skills, from other repositories
lineth-quickstart
Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or local L1 finality. Use whenever you are working inside the lineth-stack quickstart and need to boot or run the stack…
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
summarize
A guide for turning conversations, logs, documents, or investigation notes into short, action-oriented summaries. It requires conclusions to be tied to available evidence and distinguishes confirmed facts from items still needing confirmation.