Borrowing it
Nothing to install: this file belongs to dorukardahan/twitterapi-io-mcp. 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/dorukardahan/twitterapi-io-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/dorukardahan/twitterapi-io-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/instructions/dorukardahan/twitterapi-io-mcp/agents-md)<a href="https://agentmods.dev/instructions/dorukardahan/twitterapi-io-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/dorukardahan/twitterapi-io-mcp/agents-md.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.1 | $0.00576 | $0.00576 |
| Opus 5 | $0.00288 | $0.00288 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
twitterapi-io-mcp 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 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure
index.js: Main MCP server (ESM) and CLI entrypoint (twitterapi-io-mcp).data/docs.json: Bundled documentation snapshot used at runtime.scrape-all.cjs,scrape-docs.cjs: Dev-only scrapers to refreshdata/docs.json(not shipped to npm).test/index.test.js: Node.js built-in test runner suite.packages/twitterapi-docs-mcp/: Legacy npm package (deprecated wrapper for backwards compatibility)..github/workflows/: CI/release automation.cache/: Local runtime cache (gitignored; don’t commit generated content).
Build, Test, and Development Commands
Prereq: Node.js >=18.18.0.
npm install # install deps
npm start # run MCP server locally (stdio)
npm test # run unit tests (node --test)
npm run scrape # refresh docs snapshot (updates data/docs.json)
npm run build # no-op (package is pure ESM)
If you change the docs snapshot, commit data/docs.json and ensure npm test passes.
Coding Style & Naming Conventions
- JavaScript ESM (
"type": "module"); preferimport/exportandconst. - Match existing formatting in
index.js/test/index.test.js(2-space indent, minimal diffs). - Keep tool/resource identifiers stable and descriptive (e.g.,
search_twitterapi_docs,twitterapi://guides/pricing). - If you add/rename tools or resources, update the tables in
README.md.
Testing Guidelines
- Tests run with Node’s test runner; keep them deterministic and offline (no network calls).
- Add new coverage alongside existing suites in
test/index.test.jsunless a new file is clearly warranted. - Prefer
node:assertand small, focused cases (input validation, search behavior, data shape).
Commit & Pull Request Guidelines
- Commit messages are short and imperative (e.g., “Add …”, “Fix …”).
- Release/version commits typically use
vX.Y.Z - …; includeCHANGELOG.mdandpackage.jsonupdates when applicable. - Every npm publish must have a matching Git tag + GitHub Release for the same version (never let releases/tags lag npm).
- PRs should include: a clear description, how to test (
npm test), and any data/doc changes (e.g., regenerateddata/docs.json).
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 · 51 lines · 576 tokens per session scan A c78a77293ef6
twitterapi-io-mcp AGENTS.md is an instructions file published in the GitHub repository dorukardahan/twitterapi-io-mcp (8 stars, last pushed 4d ago), licensed MIT. It adds 576 tokens to every session, about $0.0029 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.