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/okasi/bot-signal/agents-mdgit clone --depth 1 https://github.com/okasi/bot-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/okasi/bot-signal/agents-md)<a href="https://agentmods.dev/instructions/okasi/bot-signal/agents-md"><img src="https://agentmods.dev/badge/instructions/okasi/bot-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.02641 | $0.02641 |
| Opus 5 | $0.01321 | $0.01321 |
| Sonnet 5 | $0.00528 | $0.00528 |
| Haiku 4.5 | $0.00264 | $0.00264 |
Grade A, and why
bot-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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents and contributors working on the bot-signal package (npm name: bot-signal, GitHub: okasi/bot-signal). It exports isHuman() etc. as the simple entry points plus full detection APIs.
Project overview
TypeScript npm library with three detection layers:
| Layer | Entry point | Location |
|---|---|---|
| Instant (browser) | detectInstantClient |
src/detectInstantClient.ts, src/checks.ts, src/asyncChecks.ts, src/webgpu.ts |
| Behavioral (browser) | createBehavioralClientDetector |
src/behavioral/ |
| Server (Node) | detectServerClientAsync |
src/server/ |
src/automation.ts contains the shared best-effort attribution result types.
Instant and server results expose automation (kind, confidence, evidence,
and alternatives); stealth framework names are probabilistic, not definitive.
src/userAgent.ts contains shared scripting-client and conservative
bot/HTTP-client/automation User-Agent token parsing.
Entry points: src/index.ts (full API), src/browser.ts (browser-only),
src/server.ts (server-only). The package.json exports map routes the root
import to the browser build under the browser condition so browser bundlers
never see node:fs. src/version.ts provides VERSION. Build output: dist/ (tsup — ESM + CJS + IIFE
browser.global.js for CDNs).
Repository layout
src/
index.ts # root entry (full API)
browser.ts # browser entry (instant + behavioral)
server.ts # server entry (server detection only)
automation.ts # shared automation attribution types/helper
userAgent.ts # shared scripting/bot/HTTP-client/automation UA parser
detectInstantClient.ts # instant detection entry
checks.ts # high-value browser checks
asyncChecks.ts # CDP, permissions, UA-CH, media devices, worker WebDriver/OS/WebGL checks
webgpu.ts # shader-f16 + isChromiumBrowser
behavioral/
analysis.ts # mouse/touch/CDP-input/scroll/typing heuristics
scoring.ts # weighted score aggregation
index.ts # detector (DOM event listener lifecycle)
types.ts
server/
geoip.ts # doc999tor-fast-geoip wrapper
ipLists.ts # parseIp + interval matching (IPv4/IPv6, binary search)
enrich.ts # auto-fill context from clientIp
analysis.ts # request contradictions + trusted crawler-verification verdict
scoring.ts # detectServerClient(Async)
tls.ts # JA3 blocklist + UA mismatch
timezone.ts # TZ offset + accept-language checks
types.ts
data/ # bundled blocklists (shipped in npm package)
docs/ # GitHub Pages demo source (index.html + app.js)
scripts/build-site.ts # builds .pages/ with dist/browser.js + stamped asset URLs
scripts/update-ip-data.ts # fetches and writes data/*.csv
test/ # vitest unit + patchright browser tests
fixtures/harness.html # DOM fixtures for browser tests
helpers/ # test server + patchright harness
patchright/ # real Chromium tests via patchright
.github/workflows/
ci.yml # typecheck + unit + patchright + build (Node 22+)
pages.yml # build .pages/ and deploy via GitHub Pages Actions
publish.yml # publish to npm on v* tags
update-ip-data.yml # weekly blocklist refresh
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 · 218 lines · 2,641 tokens per session scan A d92d06076ce4
bot-signal AGENTS.md is an instructions file published in the GitHub repository okasi/bot-signal (545 stars, last pushed 5d ago), licensed MIT. It adds 2,641 tokens to every session, about $0.0132 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-30.
Other instructions, from other repositories
redamon AGENTS.md
AGENTS.md instructions for samugit83/redamon, covering redamon - agent ruleset (repository root), auto-invoke skills, critical rules - non-negotiable, code comments and tech stack.
stride-gpt AGENTS.md
AGENTS.md instructions for mrwadams/stride-gpt, covering agents.md, what this project is, repository layout, how the agentic analysis works and progressive disclosure pattern.
Cybermes AGENTS.md
Instructions for Zyrexnn/Cybermes, covering 🛡️ cybermes master operational directives (agents.md), 1. 🎯 persona & core mission, 2. ⚡ core operational principles, 3. 📁 strict target-scoped workspace & deliverables and mandatory rules for file creation.
security-weekly-mcp AGENTS.md
AGENTS.md instructions for astroicers/security-weekly-mcp, covering agents.md — security-weekly-mcp 開發慣例(人機一體適用), 目錄導覽, 語言與風格, 分支與提交 and 分支流(2026-08-21 起).
saas-cybersecurity AGENTS.md
Instructions for YankielDBC2/saas-cybersecurity, covering agent working agreement, purpose, rules, repository map and definition of done.
kafka-mcp-enterprise-server copilot-instructions.md
Instructions for vaquarkhan/kafka-mcp-enterprise-server: Follow the repository root AGENTS.md for all work in this project.