agentmods.dev

mcp-server-nodejs-api-docs AGENTS.md

Repository instructions for coding agents working on the Node.js API documentation server.

In plain words
What is it for?
Use them when modifying code, documentation, tests, configuration, or release-related files in that repository.
Why use it?
They tell an agent which project documents define the rules, architecture, testing process, and release work, reducing the risk of changes that ignore repository expectations.

Instructions file for CodexOpenCode

11 3d ago A scan 357 tokens copy · 100% Apache-2.0
View the source file lirantal/mcp-server-nodejs-api-docs
Install

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.

agentmods
npx agentmods add instructions/lirantal/mcp-server-nodejs-api-docs/agents-md
Clone the repo
git clone --depth 1 https://github.com/lirantal/mcp-server-nodejs-api-docs

Made for: Codex, OpenCode.

Per session 357 This file is loaded in full into every session.
When invoked 357 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00357 $0.00357
Opus 5 $0.00179 $0.00179
Sonnet 5 $0.00071 $0.00071
Haiku 4.5 $0.00036 $0.00036

Measured 2d ago against content hash ef27705e3cce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-server-nodejs-api-docs 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 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.

Origin

This is a copy

100% identical to ls-mcp AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 36 lines

What it actually says

AGENTS.md

Guidance for AI coding agents working in this repository.

Start Here

Before making changes, read:

  • CONTRIBUTING.md for contribution, PR, testing, commit, and agent-specific expectations.
  • RELEASE.md for release workflow details.
  • README.md for user-facing behavior, install/use examples, and package or app overview.
  • docs/README.md for the project documentation index.
  • docs/development.md for local setup and development workflows.
  • docs/testing.md for test strategy, commands, and verification expectations.
  • docs/architecture.md for project structure, boundaries, and important invariants.
  • docs/conventions.md for project-specific coding, documentation, and maintenance conventions.

Treat those files as the source of truth. Do not duplicate or reinterpret their rules here.

Documentation

  • Keep documentation in sync when changing behavior, public interfaces, workflows, architecture, configuration, or operational assumptions.
  • Put project-specific development details in docs/; keep root files focused on their standard audiences.
  • Prefer linking to the source of truth over duplicating long instructions across files.
  • When adding new docs, link them from docs/README.md and update this file only when they become important entry points for future agents.

PRs and Issues

  • Follow PR, issue, and agent-labeling rules in CONTRIBUTING.md.
  • Use the issue-linking format specified in CONTRIBUTING.md.

Releases

  • Follow RELEASE.md for release workflow and changeset creation steps.
  • If this project uses changesets, treat RELEASE.md and any changeset guidance in CONTRIBUTING.md as authoritative.
Changes

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.

  1. 2d ago First seen · 36 lines · 357 tokens per session scan A ef27705e3cce

Subscribe to this mod's changes

mcp-server-nodejs-api-docs AGENTS.md is an instructions file published in the GitHub repository lirantal/mcp-server-nodejs-api-docs (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 357 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ls-mcp AGENTS.md, differing in 0 lines, and is treated as a copy.

Backend and APIsGit and workflowLLMTestingclaude-aiclaude-desktopcursorcursor-aimcp
Related

Other instructions, from other repositories

ls-mcp AGENTS.md

Instructions for lirantal/ls-mcp, covering agents.md, start here, documentation, prs and issues and releases.

lirantal/ls-mcp · 357 tokens

claude-faf-mcp CLAUDE.md

Instructions for Wolfe-Jam/claude-faf-mcp, covering claude.md — claude-faf-mcp, what this is, stack and context.

Wolfe-Jam/claude-faf-mcp · 240 tokens

cosmos-mcp CLAUDE.md

Instructions for teampolarity/cosmos-mcp, covering cosmos-mcp, layout, tools (authoritative list in src/tools/index.ts), cli subcommands and imessage is the headline source.

teampolarity/cosmos-mcp · 1,310 tokens

mcp-httpserver-proxy AGENTS.md

Instructions for shailesh17/mcp-httpserver-proxy, covering agent guidelines for mcp-httpserver-proxy, 🎯 repository overview, ⚠️ critical constraints & rules, 1. standard output (stdout) is sacred and 2. transport lifecycle order.

shailesh17/mcp-httpserver-proxy · 861 tokens

claudit-sec CLAUDE.md

Instructions for HarmonicSecurity/claudit-sec, covering claudit-sec — claude security audit tool, project overview, architecture, data collectors and key paths.

HarmonicSecurity/claudit-sec · 2,074 tokens

docmost-local-mcp CLAUDE.md

Instructions for wisflux/docmost-local-mcp, covering claude.md, response style, what this is, commands and run the mcp server locally (talks mcp over stdio).

wisflux/docmost-local-mcp · 2,174 tokens