Borrowing it
Nothing to install: this file belongs to Lianye-Scythe/scythe-context-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/Lianye-Scythe/scythe-context-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Lianye-Scythe/scythe-context-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/lianye-scythe/scythe-context-mcp/agents-md)<a href="https://agentmods.dev/instructions/lianye-scythe/scythe-context-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lianye-scythe/scythe-context-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/lianye-scythe/scythe-context-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lianye-scythe/scythe-context-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00356 | $0.00356 |
| Opus 5 | $0.00178 | $0.00178 |
| Sonnet 5 | $0.00071 | $0.00071 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
scythe-context-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 12d 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
Scythe Context MCP Agent Guide
Workflow
- Start with
repo_index_statusto check whether.scythe-context/index.sqliteexists, whether files/chunks/symbols/dependencies/embeddings are present, and whether freshness reports stale files. - If metadata is missing or stale, run
repo_reindexwithdry_run=false. - Set
index_embeddings=trueonly when semantic search is needed. This sends chunk text to the configured Gemini-compatible endpoint. - Prefer
repo_context_packfor task-oriented code lookup. It combines hybrid search, snippet budgeting, related-file metadata, bounded multi-hop traversal, and suggested paths. - Use
repo_semantic_searchwhen debugging raw ranking behavior. Prefer a smallermax_context_charsfor broad exploration and increase it only when the returned snippets are not enough. - After a search result identifies a useful file, call
repo_related_filesfor that file when you need a focused view of its symbols, imports, and reverse imports.
Privacy
- Do not commit
.scythe-context/, legacy.repo-beacon/, orlocal/. - Do not print API keys, proxy tokens, or contents of files under
local/secrets/. - Treat third-party Gemini-compatible proxy endpoints as remote services that can see query and chunk text.
Development
- Keep indexing, storage, provider, search, and MCP tool wiring decoupled.
- Preserve stable chunk row ids for unchanged files so embedding cache remains useful.
- Add focused tests when changing scanner, chunker, schema, ranking, formatting, or provider compatibility.
- Run
npm test,npm run build, andnpm audit --omit=devbefore committing a completed development slice.
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.
- 12d ago First seen · 24 lines · 356 tokens per session scan A c80ac7239334
scythe-context-mcp AGENTS.md is an instructions file published in the GitHub repository Lianye-Scythe/scythe-context-mcp (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 356 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
repobrain copilot-instructions.md
Copilot instructions for study8677/repobrain, covering github copilot bootstrap instructions and hard rule — query the repobrain hub first.
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.
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).
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.