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 instructions/ishan-parihar/threads-lyr/agents-mdgit clone --depth 1 https://github.com/ishan-parihar/threads-lyrWrote 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/ishan-parihar/threads-lyr/agents-md)<a href="https://agentmods.dev/instructions/ishan-parihar/threads-lyr/agents-md"><img src="https://agentmods.dev/badge/instructions/ishan-parihar/threads-lyr/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.00369 | $0.00369 |
| Opus 5 | $0.00185 | $0.00185 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
threads-lyr 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 4d 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
AGENTS.md — threads-lyr
What this is
A standalone Threads.net MCP server cloned from facebook-lyr and stripped to
Threads-only (anonymous read). Two read tools + one session tool.
Architecture
threads_mcp_server/scraping/api_client.py— anonymous client; fetchesthreads.net/@usernamewith curl_cffi Chrome impersonation. No cookies.threads_mcp_server/scraping/parsers.py— recursive deep-scan of embedded JSON script blocks (Next.jspageProps).threads_mcp_server/tools/threads_tools.py— FastMCP tool registration.threads_mcp_server/server.py— server assembly;create_mcp_server().threads_mcp_server/cli_main.py— AXI-compliant CLI (home view, flags).threads_mcp_server/config/— layered config, no cookie/auth concerns.
Conventions
- Mirror facebook-lyr conventions exactly (AXI output, tool_guard decorator, FastMCP DI pattern, TOON output, error_handler mapping).
- All tools are read-only: annotate
{"readOnlyHint": True, "openWorldHint": True}. - Never add cookie/login/auth machinery — Threads profiles are public.
- Publish-side features belong behind the official Threads API (future work).
Testing
uv run pytest -q # parsers, client (FakeSession), server, CLI
uv run ruff check . && uv run ruff format --check .
Environment
THREADS_TRACE_DIR— optional trace log directory.TRANSPORT,HOST,PORT,HTTP_PATH,LOG_LEVEL— server config.
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.
- 4d ago First seen · 38 lines · 369 tokens per session scan A f4c265acc8af
threads-lyr AGENTS.md is an instructions file published in the GitHub repository ishan-parihar/threads-lyr (0 stars, last pushed 24d ago), licensed MIT. It adds 369 tokens to every session, about $0.0018 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).
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.
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).