Borrowing it
Nothing to install: this file belongs to anotb/x-signal. 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/anotb/x-signal/main/AGENTS.mdgit clone --depth 1 https://github.com/anotb/x-signalWrote 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/anotb/x-signal/agents-md)<a href="https://agentmods.dev/instructions/anotb/x-signal/agents-md"><img src="https://agentmods.dev/badge/instructions/anotb/x-signal/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.00491 | $0.00491 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
x-signal 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 5d 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 — 23 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with X Signal
Installing for a user
- Detect the operating system and confirm Docker Compose is available before changing anything.
- Keep the default services and ports bound to loopback.
- Start with
docker compose up -d --build --wait, then check/healthz,/readyz, anddocker compose ps. - Connect local Codex clients to
http://127.0.0.1:7345/mcp. - Never ask a user to paste cookies, session tokens, VNC passwords, tunnel URLs, or other credentials into chat.
- Prefer a dedicated Chrome profile with the session companion. A profile selected during active research is queued and should complete through automatic sync; do not ask for a second activation click. Use noVNC for visible sign-in or challenge recovery.
- Do not bypass X authentication, challenges, access controls, or rate limits.
- For ChatGPT web, use the opt-in
chatgptSecure MCP Tunnel profile. Help the user create a workspace-associated tunnel and a runtime key restricted to Tunnels Read + Use, then ask them to enter both directly intonpm run tunnel:secure:configure; its key prompt is hidden. Never capture, print, repeat, or commit either value. Usenpm run tunnel:chatgptonly as an explicitly short-lived fallback, and never expose port 7345 directly. - Explain every visible step the user must perform and verify the final X identity without repeating its handle in public logs.
Changing the project
- Keep the architecture tool-only unless a real user workflow requires UI.
- Preserve one persistent browser, concurrency two, request spacing, durable jobs, account-bound provenance, and adaptive backoff.
- Do not add posting, generic browser automation, CAPTCHA handling, proxy rotation, or enforcement-evasion features.
- Use synthetic parser fixtures. Never commit captured posts, account handles, browser data, exports, registrations, tunnel identifiers, credentials, temporary URLs, or local paths. The only image exception is an explicitly allowlisted public showcase capture under
docs/assetsthat has been manually checked againstSECURITY.md. - Run
npm run validate,npm audit --audit-level=moderate,docker compose config --quiet, and the plugin/skill validators before release. - Treat live tests as real account traffic. Use the smallest canary that proves the change and do not leave test monitors running.
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.
- 5d ago First seen · 23 lines · 491 tokens per session scan A 377d0bc48786
x-signal AGENTS.md is an instructions file published in the GitHub repository anotb/x-signal (1 stars, last pushed 22d ago), licensed MIT. It adds 491 tokens to every session, about $0.0025 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
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.
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).
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).
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.
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.