Borrowing it
Nothing to install: this file belongs to SunrisesIllNeverSee/sigrank-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/SunrisesIllNeverSee/sigrank-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/SunrisesIllNeverSee/sigrank-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/sunrisesillneversee/sigrank-mcp/agents-md)<a href="https://agentmods.dev/instructions/sunrisesillneversee/sigrank-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sunrisesillneversee/sigrank-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.01797 | $0.01797 |
| Opus 5 | $0.00898 | $0.00898 |
| Sonnet 5 | $0.00359 | $0.00359 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
sigrank-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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SigRank MCP — Agent Rules
Quick reference
| What | Command |
|---|---|
| Unit tests | node test.mjs (313 assertions) |
| Signing tests | node sign.test.mjs |
| Run CLI locally | node index.mjs (TUI if TTY, MCP server if piped) |
| Install deps | npm install |
Bun (faster alternative): All commands work with Bun (~10-30x faster):
| What | Bun command |
|---|---|
| Install deps | bun install |
| Unit tests | bun test.mjs |
| Signing tests | bun sign.test.mjs |
| Run CLI locally | bun index.mjs |
| Run published CLI | bunx sigrank (same as npx sigrank but faster) |
Bun is installed at ~/.bun/bin/bun (v1.3.13). It reads the same package.json
and package-lock.json — no migration needed. Use bunx instead of npx for
one-off package execution.
Publishing
Auto-publish is ON (2026-07-31). Push to main triggers .github/workflows/publish.yml,
which runs tests, bumps the patch version, publishes to npm, pushes the version
commit back to main, and dispatches a sync-mcp-version event to sigrank-app
(so the app's MCP_VERSION constant auto-updates → Vercel auto-deploys).
Do NOT manually run npm publish or npm version. The workflow handles it.
If you need to publish manually (e.g. the workflow is broken), bump the patch
version in package.json, commit, push, and the workflow will handle the rest.
Do NOT add npm publish or npm version to commit messages or scripts.
The workflow does this automatically. Manual publishes create duplicate versions.
Version scheme: 1.0.x (graduated from 0.0.x on 2026-08-27). The patch
(third decimal) increments on every release: 1.0.0 → 1.0.1 → 1.0.2 → ...
Never use minor bumps (1.1.x, 1.2.x) or major jumps (2.0.x). The 0.0.x format
was retired because legacy 0.17.x/0.18.x/0.19.x versions sorted higher in
semver (0.17.2 > 0.0.232), causing the MCP Registry to show a stale version
as "latest." Graduating to 1.0.x fixes this (1.0.0 > 0.19.0 > 0.17.2).
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.
- yesterday Changed · +87 lines · +723 tokens per session b238cee57301
- 6d ago First seen · 101 lines · 1,074 tokens per session scan A 0c072e4c2dd0
sigrank-mcp AGENTS.md is an instructions file published in the GitHub repository SunrisesIllNeverSee/sigrank-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 1,797 tokens to every session, about $0.0090 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.