Borrowing it
Nothing to install: this file belongs to evex-dev/linejs. 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/evex-dev/linejs/main/AGENTS.mdgit clone --depth 1 https://github.com/evex-dev/linejsWrote 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/instructions/evex-dev/linejs/agents-md)<a href="https://agentmods.dev/instructions/evex-dev/linejs/agents-md"><img src="https://agentmods.dev/badge/instructions/evex-dev/linejs/agents-md/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/instructions/evex-dev/linejs/agents-md"><img src="https://agentmods.dev/badge/instructions/evex-dev/linejs/agents-md.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.00630 | $0.00630 |
| Opus 5.5 | $0.00252 | $0.00252 |
| Sonnet 5.5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
linejs AGENTS.md 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 2mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a Deno-first monorepo.
packages/linejs: main TypeScript library (@evex/linejs) with feature modules underclient,base, andthrift.packages/types: shared LINE type definitions (@evex/linejs-types).docs: VitePress documentation site and content.example: runnable examples for browser, node, talk, square, storage, thrift, etc.scripts: generation/utility scripts, including thrift tooling and service/type helpers.resources: static assets used by the project.
README.md in the root points to packages/linejs/README.md for package-level context.
Build, Test, and Development Commands
deno task dev: run local sandbox (workspace root).deno task docs:dev: run docs dev server fromdocs.deno task docs:build: build docs fromdocs.cd docs && npm run dev|build|serveorbun run dev|build|serve: alternate docs workflows.deno test: run the Deno test suite (CI uses this at repository root).cd packages/linejs && deno test: run package-scoped tests.deno fmt: apply repository formatter (configured indeno.json).
Coding Style & Naming Conventions
- Use Deno formatter settings from repo: tabs for indentation, double quotes in most files.
- Keep TypeScript across all source files and prefer explicit typing for public APIs.
- Use clear, domain-based names:
camelCasefor functions/variables,PascalCasefor classes/types. - File names are typically kebab-case or snake-like and placed under relevant feature folders (
client/features/*,base/*).
Testing Guidelines
- Test framework: Deno’s built-in test runner.
- Test files use
*_test.tsnaming, e.g.packages/linejs/base/core/typed-event-emitter/index.test.ts. - Run tests before PRs:
deno testor package-scoped commands above. - Add/adjust unit coverage when changing logic in touched files; keep existing test conventions.
Commit & Pull Request Guidelines
- Commit history mostly follows Conventional Commit style (
feat:,fix:,chore:,testing:). - Use short, imperative summaries, e.g.
feat(client): add message retry logic. - PR description should explain behavior changes and testing performed.
- Include reproduction notes when behavior depends on credentials, protocol behavior, or network-sensitive paths.
- Optional checklist items in
.github/pull_request_template.md: tests, jsdoc updates, local runtime checks.
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.
- 2mo ago First seen · 47 lines · 630 tokens per session scan A e88bba60f580
linejs AGENTS.md is an instructions file published in the GitHub repository evex-dev/linejs (419 stars, last pushed 19d ago), licensed MIT. It adds 630 tokens to every session, about $0.0025 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.